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 classes and workshops.
Chris offers numerous resources for learning the microservice architecture.
Chris teaches comprehensive workshops and training classes for executives, architectures and developers to help 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.
Want to see an example? Check out Chris Richardson's example applications. See code
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.
Alternatively, conduct a self-assessment using the Microservices Assessment Platform.
Join the microservices google group
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
Application architecture patterns
Decomposition
Data management
Transactional messaging
Testing
Deployment patterns
Cross cutting concerns
Communication style
External API
Service discovery
Reliability
Security
Observability
UI patterns