How do companies ship code to production? The following describes a typical software delivery workflow. Companies have diverse environments using different tools, so this is one representative workflow that demonstrates some common practices. Details will differ across organizations. With that context established, the general steps are as follows: Step 1: The product owner creates requirements and stories. Step 2: The development team prioritizes stories and organizes sprints. Step 3: Developers commit code to the version control system. Step 4: An automation server builds the code and runs tests. Code coverage and quality checks are performed. Step 5: If the build succeeds, artifacts are stored in the artifact repository. The build is then deployed to the developer environment. Step 6: Features are tested independently in multiple isolated environments. Step 7: The QA team tests the features in QA environments. Various forms of testing are performed. Step 8: Once verified, the build is deployed to a user acceptance testing environment for final validation. Step 9: Release candidates that pass testing can be deployed to production based on the release schedule. Feature flags and incremental rollout techniques are used to manage risk. Step 10: The site reliability team monitors production and reports issues. Teams prioritize and fix issues according to defined policies. How does your organization's software delivery workflow differ from the process outlined here? What tools and techniques have you found most effective? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/496keA7
@sahnlam Can someone explain me role and responsibility of 'SRE'? Thanks.
@sahnlam Some components can changes but the steps are there. Now let’s wait the solopreneur shouting 🤣