881 bytes added
, 31 January
Are your architecture and the current state of your software ready for Continuous Delivery?
Topics you might want to consider are:
* Is your software built as one giant monolith, or is it divided into multiple components?
* Can you deliver parts of your application separately?
* Can you guarantee the quality of your software when deploying multiple times a week?<ref>If this question makes you laugh out loud because you struggle to release software once in 3 months, then No, you're not ready</ref>
* How do you test your software?
* Do you run one or multiple versions of your software?
* Can you run multiple versions of your software side by side?
* What do you need to improve to implement Continuous Delivery?
To learn some basics about Continuous Delivery, see the short tutorial at https://learn.microsoft.com/en-us/training/modules/introduction-to-deployment-patterns
