Difference between revisions of "Deployment patterns"
Jump to navigation
Jump to search
(first draft) |
m (Text replacement - "Category:Continuous Deployment" to "Category:Continuous Delivery") |
||
Line 16: | Line 16: | ||
* Feature toggles | * Feature toggles | ||
− | [[Category:Continuous | + | [[Category:Continuous Delivery]] |
Revision as of 10:21, 31 January 2024
Classical deployment pattern[edit | edit source]
In a classical development and deployment environment, (monolithic) software moves in stages between environments culminating in a "feature release" like a dump truck delivering a load of dirt.
Modern deployment patterns[edit | edit source]
In a Continuous Delivery environment, where testing is encouraged in "Production", changes are not delivered in a "big bang". It's possible to deploy features without exposing them to all users.
For example:
- Blue-green deployments
- Canary releases
- Dark launching
- A/B testing
- Progressive exposure or ring-based deployment
- Feature toggles