Remove shared environment code & documentation

Signed-off-by: Philipp Hugenroth <philipph@spotify.com>
2023-07-28 14:22:57 +02:00
parent 425b386e13
commit 5cf35d1948
8 changed files with 26 additions and 320 deletions
@@ -26,7 +26,6 @@ When we set out on this project, we had a few primary goals. First, we intended
 - Make it easier to create and maintain backend installations.
 - Align how plugins provide points of customization and how those customizations are installed.
 - Make it much easier to maintain plugins, in particular keeping the API stable.
- Simplify the process of splitting plugins out into separate deployments with shared environments.
 - Improve the local development and testing experience.

 Prioritizing simplicity is often a guiding principle that we use for designs that span multiple ownership roles. We decide on which parts of the system that we think are the most important to have as simple as possible, or, viewed from the opposite end, where in the system we put necessary complexity. In this case, we optimized for keeping the backend setup as simple as possible, followed by modules and plugins, then libraries, and lastly the framework itself. What this guidance means in practice is that when there is complexity that needs to be added to implement a certain feature, we place as much of it as possible within the framework itself, then libraries, plugins and modules, and if absolutely needed, the backend setup.