Are you frustrated working with large, legacy and potentially lethal code bases? We were frustrated too, but in 4-5 years of time, we replaced A (front-end) and B (back-office) system with ~150 microservices. From the days of no tests and clumsy deployment process, we moved to each service with unit tests, CI and deploying with a bot. With the business buying in the process, we enabled the business to reach new heights. This talk reveals that journey and the things we learned along the way.
11. “
“Microservice architectural style is an approach to developing a
single application as a suite of small services, each running in its
own process and communicating with lightweight mechanisms,
often an HTTP resource API. These services are built around
business capabilities and independently deployable by fully
automated deployment machinery”
- Martin Fowler
Source: https://martinfowler.com/articles/microservices.html
12. “
“Microservices is an architectural style that structures an
application as a collection of loosely coupled services, which
implement business capabilities. The microservice
architecture enables the continuous delivery/deployment of
large, complex applications. It also enables an organization to
evolve its technology stack”
- Chris Richardson
Source: http://microservices.io/