You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ARCHITECTURE.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,13 +14,18 @@ Standard is a _framework_ to bootstrap and sustain the automatable sections of t
14
14
In particular, Standard is a _Horizontal Integration Framework_ which integrates _vertical_ tooling, that is designed around the linux philosophy of doing one thing and to it well.
15
15
The integration target, thereby, are the end-to-end automatable sections of the SDLC process for which we offer well-integrated tools and best practices.
16
16
_Efficient_ automatable sections of the SDLC are characterized by two things.
17
+
17
18
Firstly, an adequate _lead time_ which is the amount of time it takes to set up an initial version of the software delivery pipeline.
18
-
It needs to be "adequate" rather than "just fast", because it takes place in the context of a team and thus encompasses learning and onboarding activities.
19
-
Rather than optimizing for speed, these need optimization for success, above all.
19
+
It needs to be _adequate_ rather than _just fast_, as it takes place in the context of a team and thus encompasses learning and onboarding activities.
20
+
Rather than optimizing for speed, these need optimization for success.
21
+
20
22
Secondly, efficient automatable sections of the SDLC are characterized by short _cycle times_ which is the amount of time it takes for a commit to be shipped to a production environment.
21
-
Along this journey, we encounter aspects of the development, or in the broader sense, the _contribution_ environment.
22
-
We also encounter the packaging pipeline that produces our distributable artifacts.
23
-
We encounter Continuous Building & Integration, Continuous Deployment as well as Continuous Observability and Discovery.
23
+
Along this journey, we encounter our scope (more on it below):
24
+
25
+
- aspects of the _contribution_ environment;
26
+
- the packaging pipeline that produces our distributable artifacts;
27
+
- Continuous Building & Integration, Continuous Deployment as well as Continuous Observability and Discovery.
28
+
24
29
The goal of Standard is to optimize the critical path along this process to achieve superior _cycle times_ through the powers of Nix and Flakes when compared to any other similar framework that doesn't recognize the intrinsic value of _reproducability_.
0 commit comments