Microservice architecture patterns and best practices

Today, there are several trends that are forcing application architectures to evolve. Users expect a rich, interactive and dynamic user experience on a wide variety of clients including mobile devices. Applications must be highly scalable, highly available and run on cloud environments. Organizations often want to frequently roll out updates, even multiple times a day. Consequently, it’s no longer adequate to develop simple, monolithic web applications that serve up HTML to desktop browsers.

This site describes a new, alternative architecture: microservices. Applications with a microservice architecture consist of a set of narrowly focused, independently deployable services. Read on to find out more about this approach and its associated trade-offs.

A good starting point is the Monolithic Architecture pattern.

Microservices consulting and training

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action and the creator of the original CloudFoundry.com. His latest startup is eventuate.io, a microservices application platform.

He offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, consulting, workshops and hands on training classes.

Learn More

The patterns

• Monolithic architecture
• Microservices architecture
• API gateway
• Client-side discovery
• Server-side discovery
• Service registry
• Self registration
• 3rd party registration
• Multiple service instances per host
• Single service instance per host
• Service instance per VM
• Service instance per Container
• Serverless deployment
• Database per Service
• Microservice chassis
• Shared database
• Event-driven architecture
• Event sourcing
• CQRS
• Transaction log tailing
• Database triggers
• Application events

A new microservices application platform that solves distributed data management problems.

Learn more

Join the microservices google group