Seven Ways to Fail at Microservices

InfoQ Dev Summit Boston, a two-day conference of actionable advice from senior software developers hosted by InfoQ, will take place on June 24-25, 2024 Boston, Massachusetts.

Deep-dive into 20+ talks from senior software developers over 2 days with parallel breakout sessions. Clarify your immediate dev priorities and get practical advice to make development decisions easier and less risky.

----------------------------------------------------------------------------------------------------------
Holly Cummins discusses a number of anti-patterns in building microservices: The murky goal, Microservices envy, Cloud native spaghetti, The enterprise hairball, The someday automation, and others.

#Microservices #Antipatterns #Patterns

[xxtvccy]

We at my company make it mandatory when we roll onto new projects with new Clients. The second there's a bunch of microservices, we mandate that a Pact broker is installed straight away, because we already know that they will have e2e tests in the environments blurry the lines making testing more of a nightmare. Testing can be very simple. People over complicate things with "integration" tests and "e2e" tests, making sure that a service talks to another and it's not broken with a new update. When you insert contract testing in these places, it becomes a much more clear and organised domain.

[krumbergify]

Great talk! I have fallen into almost every trap there is 😄

[bfg]

Contract testing sounds promising, given you invest in automation (producer "shares" contract for a new version, consumers pick it up at their own tempo, generates tests for the definition - with diffs, and adjust). Otherwise it'll be just another blocker for independent delivery.

[nitinkarve]

This is really really nice and informative talk around ms. MS should not be for CV :)

[michaeldeng]

Perhaps most of companies don't need microservices

[guriysamarin]

Thanks! Deep content concisly explained

[anindyadey]

Old school integration tests would easily solve this problem between both service teams

[ianmarteens]

First way to fail at microservices: just having a look at they.

[dylam]

your siloed comrades: "we don't know if our code works...",
me: "ofc, your project has less than 70% code coverage in tests. Obviously, you ain't giving me a complete plate of spaghetti, not that I wanted spaghetti in the first place..."

[oeaoo]

Mindlessness is the most common problem in my view.

[stanleymasinde_]

Microservices vs Distributed monoliths.

[dgaborus]

One of the biggest disaster that ever struck this profession is the microservices-religion. To serve a 7 page Angular frontend, some teams build a microservices spiderweb consisting of 50 services just to make sure every vendor has a job.