Welcome to the first of what is hopefully a regular roundup of what’s new and relevant in the world of microservices. In the past week:
Russ Miles (@russmiles) announced µCon, the first conference about microservices. It takes place in London on November 27th-28th.
Martin Fowler (@martinfowler) published the final installments of his in-depth article about microservices.
Arnon Rotem-Gal-Oz compared microservices with SOA and argued that “microservices” is not a good term.
Gawain Hammond (@gawainhammond) wrote a blog post on microservices defending the term “microservices”.
@rrees wrote in interesting summary of a session on microservices at the Scale Summit.
Chris Richardson (@crichardson) published Thoughts about #microservices – less micro, more service? that suggested that there should be more emphasis on “service” and less on “micro”.
There was also the ongoing twitter discussion.
And then there was this:
#microservices pic.twitter.com/T7XOjcUE73
Tom Janssens (@ToJans) March 25, 2014
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.
Got a question about microservices?
Fill in this form. If I can, I'll write a blog post that answers your question.
I help organizations improve agility and competitiveness through better software architecture.
Learn more about my consulting engagements, and training workshops.
Chris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
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 NPXJKULI to sign up for $95 (valid until December 25th, 2024). 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.
Join the microservices google group
Note: tagging is work-in-process
Cynefin · DDD · GitOps · Microservices adoption · ancient lore · anti-patterns · api gateway · application api · application architecture · architecting · architecture · architecture documentation · assemblage · automation · beer · books · build vs buy · containers · culture · dark energy and dark matter · decision making · deployment · deployment pipeline · design-time coupling · developer experience · development · devops · docker · eventuate platform · fast flow · generative AI · glossary · health · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservices rules · microservicesio updates · modular monolith · multi-architecture docker images · observability · pattern · pattern language · refactoring · refactoring to microservices · resilience · sagas · security · service api · service architecture · service blueprint · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · survey · tacos · team topologies · technical debt · testing · transaction management · transactional messaging · wardley mapping
Application architecture patterns
Decomposition
Refactoring to microservicesnew
Data management
Transactional messaging
Testing
Deployment patterns
Cross cutting concerns
Communication style
External API
Service discovery
Reliability
Security
Observability
UI patterns