Microservices is an increasingly popular architecture style that promotes scalability and ease of testing and deployment through small, highly distributed service components. It may sound like the correct architecture for your situation, but if you’re new to microservices, how do you really know? Understanding microservices’ pitfalls (practices that are never a good idea) and anti-patterns (practices that seem like a good idea, but aren’t) is a good place to start. In this video, 20+ year software architecture veteran Mark Richards (IBM, CSC, etc.) doesn’t just identify the pitfalls and anti-patterns of microservices, he shows you how to avoid them. You’ll learn about service granularity estimation, database migration, microservices reporting, distributed transaction management, remote access latency, contract versioning, distributed logging, and much more.

Understand how to recognize and avoid costly microservices development mistakes

Survey each of the 10 most common pitfalls associated with microservices

Get wise to the 6 hidden anti-patterns that can ruin a microservices effort

Master the knowledge required to stay clear of these pitfalls and anti-patterns

Tap into an assessment tool that tells you if you truly understand microservices development

Learn to determine if microservices is the right architecture style for your situation

Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures, service-oriented architectures, and distributed systems in J2EE and other technologies. He worked for twenty plus years as a software architect for heavyweights like IBM and CSC. He founded the New England Java Users Group and is the author or co-author of sixteen O'Reilly titles including Microservices vs. Service-Oriented Architecture, Service-Based Architectures, 97 Things Every Software Architect Should Know, and Software Architecture Patterns.