Practical Application - Evolving architecture
3 important questions on Practical Application - Evolving architecture
What are problems of modern applications?
- (small) changes in one part can lead to negative effects in other parts
- resources for coordination because developers work simultaneously on the functionality
- very few employees understand the IT system landscape holistically
- documentation on the IT system becomes quickly obsolete
- development en operation are separeated, so operation employees have to escalate relatively simple questions
- it is difficult to identify reponsibility areas for small self-sufficient teams
- existing architecture does not fully address current requirements, it is soon obsolete
- changing and developing the architecture is difficult because of the large number of rigid links
What is the advantage of share nothing principle?
- It makes it possible to work independently of others and by dedicated teams.
- It makes it possible to use the basis DevOps principles: value stream, deployment pipeline, keeping everything in the version control system, automated configuration management and the definition of done.
- Evolving the architecture when there are new business requirements of novelties and so the possibility to reduce technical debt.
What is the best approach to make the change from a monolithic to an microservices architecture?
Upgrade the architecture as continual activity and treat it as a part of the regular development work with each next business request.
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding
Remember faster, study better. Scientifically proven.
