How author went about his goal – to come up with an overarching technical vision for the whole company aligned with their 3-year business strategy, and that would move us away from a monolithic architecture and central SRE team to a distributed system where we shift ownership to each team. By Daniel Micol.
To accomplish the goal, author started working with other engineers and product leaders to understand the history of our technical architecture and the challenges that we were facing including developer productivity issues, site reliability problems or scalability limitations. From these goals, we derived a set of requirements for our 3-year technical vision:
- Features
- Leveraging Data
- Performance
- Scale
- Quality
- Self-Service
- Development Process
We must streamline our internal development processes and progress along the DevOps Big 4 to these levels: Deployment frequency: Elite (Daily for web and backend services and up to weekly for native apps), Lead time for changes: Elite (Less than one hour), Mean time to restore service: Elite (Less than one hour), and Change failure rate: Elite (0-15%).
We liked sOme interesting thoughts around development process. To learn how their effort led to long-term thinking technical vision that will provide the right guidance to our teams, indicate how the different pieces in our system should fit together - follow the link to the full article. Nice one!
[Read More]