This week is the 10th anniversary of my first talk about the microservice architecture. In April 2012, I was in Kiev, Ukraine (see note below) as part of the Cloud Foundry Open Tour 2012 (Kiev, Moscow and London). At the Kiev event, I gave a new presentation Decomposing applications for deployability and scalability.
The big idea was that for some applications the monolithic architecture didn’t make sense. For these applications, better architecture is to apply Y-axis scaling of the scale cube and structure the application as a collection of independently deployable services.
At the time, I didn’t call this style of architecture microservices. That term didn’t become popular until James Lewis and Martin Fowler’s 2014 article Instead, I talked about a modular, polyglot architecture, which was too much of a mouthful to catch.
I was pleasantly surprised by the audience’s very enthusiast reception. Apparently, it covered issues that resonated with developers.
I got the same excited reaction when I gave the talk in Moscow, London, and elsewhere. So much so, that I’m still talking about microservices 10 years later!
I’m sickened by the war in Ukraine. I hope that one day Putin (along with the other 21st century war criminals) will face justice - or rot in hell.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Learn moreChris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging