Microservices With a Contract-First Architectural Approach: A Key to Scrum Success
Scrum-based development “from scratch” projects that are based on a traditional monolithic architecture are prone to failures. The objective of this article is to understand the causes—and propose a possible solution based on microservices with a contract-first architectural approach instead of the traditional monolithic architecture.
Let’s take a look at some important basic definitions:
- Agile: A method for project management, used especially for software development, characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans. (Reference: https://en.oxforddictionaries.com/definition/agile)
- Scrum: An iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal," challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved. [Reference https://en.wikipedia.org/wiki/Scrum_(software_development)]
- Microservices: Also known as microservice architecture. Is an architectural
Please log in or sign up below to read the rest of the article.