Microservices AntiPatterns and Pitfalls

by Mark Richards

Remember when service-oriented architecture (SOA) was all the rage? Companies jumped in before fully understanding SOA’s advantages and disadvantages, and struggled to make this complex architecture work. Today, we’re poised to repeat this same experience with microservices—only this time we’re prepared. With this concise ebook, author Mark Richards walks you through the ten most common microservice anti-patterns and pitfalls, and provides solutions for avoiding them.
What’s the difference between anti-patterns and pitfalls? An anti-pattern seems like a good idea when you begin, but only leads you into trouble, while pitfalls are bad ideas from the start. Learn how to avert the most flagrant anti-patterns and pitfalls before you tussle with microservice granularity, data migration, and distributed processing.
You’ll examine:
- Data-Driven Migration Anti-Pattern
- Timeout Anti-Pattern
- "I Was Taught to Share" Anti-Pattern
- Reach-in Reporting Anti-Pattern
- Grains of Sand Pitfall
- Developer Without a Cause Pitfall
- Jump On The Bandwagon Pitfall
- Static Contract Pitfall
- Are We There Yet Pitfall
- Give it a Rest Pitfall

Genres: Programming, Technology, Software, Computer Science, Engineering, Technical, Architecture

66 pages, ebook

Published July 27, 2016

About the author

There are multiple authors with this name in this data base. This one is Mark^^^Richards.

Reviews

[Angel Castro · Rating 4 out of 5]

Sort and right to the point. If you need to knowif microservices is for you, or you're a victim of the hype, you better read this small book, that sumarizes all the pros and cons, and signal all the potential problems you could face if you (or your team) start working with microservices.

[Julio Biason · Rating 4 out of 5]

Not a book per se, but a paper about the tendencies that lead to microservices to fail. If this was a book, I think I'd give it less stars, but since it is just a short paper, it feels alright -- for a book, longer content and how to implement the corrects would be nicer.

In the end, for people starting with microservices, it is a good pointer for "do not do that"; for people working with microservices for awhile, it's quite a "I did that already" checklist.

[Peter Rybarczyk · Rating 4 out of 5]

Good book, not the perfect one but a really good one.
What's important, this is not a text about "how awesome microservices are" or "how to build some shiny services", except that as the title suggests, the author, focuses mostly on "how not to build microservice". And this is the thing that should be more common in all IT books.

Reading this will show you some most common issues with one of the most powerful concepts in software architecture.

[Jared · Rating 5 out of 5]

Perfect for what it is. Very short summary of common microservice issues.

[Tetsuaki Matsumoto · Rating 5 out of 5]

Readers are able to know basic concerns and options from architects and developers viewpoint. Before getting on board microservices architecture, it's better to read.

[Catalin · Rating 5 out of 5]

It's a very short but concise book about anti patterns of micro services adoptions, it can be easily used as a introduction to familiarize with the domain.

[Abdur Rahman · Rating 4 out of 5]

Was certainly helpful. Did not know that there were transacted messaging even when using queues.

[Beltan Tonuk · Rating 5 out of 5]

Quick summary, but to the point

[Pepijn Looije · Rating 4 out of 5]

Really happy to have found this book today. It makes my life much easier now that I can talk about addressing the Reach-in Reporting Anti Pattern at work.

[Waldemar Mękal · Rating 3 out of 5]

Very practical and quick to read.

[Jakub Janeczko · Rating 4 out of 5]

Not too long, it could be a longer web article, but that's enough to introduce into the topic. Explains each problem in a very clear way and gives almost real life examples.

[Khaled Al-Ansari · Rating 4 out of 5]

Great book where the author focus on the high level without repeating or adding unnecessary details though I would love to see an updated version where he can share how the approach would change for example how the grain analysis will be if the project was using NoSQL instead of relational database.

[Viktor · Rating 5 out of 5]

Nice, lightweight, and easy-to-read book. Provides good and frequent issues with the implementation of. microservices.

[Mihai Vasilache · Rating 4 out of 5]

Short list of microservices best practices. They are already well known practices in the software industry, but this is because the book is 8 years old.

[Michael · Rating 4 out of 5]

Concise and easy to follow overview. Useful, but don't expect deep details on specific topics.

[Tomáš · Rating 4 out of 5]

Not bad, really!