Seven Ways to Fail at Microservices

[@user-xx7tv7cc1y]

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 😄

[@nitinkarve3608]

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

[@bfg5244]

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.

[@ianmarteens]

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

[@ronaldogeldres7475]

Great video! I loved it, thanks!

[@guriysamarin6204]

Thanks! Deep content concisly explained

[@anindyadey2292]

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

[@michaeldeng1981]

Perhaps most of companies don't need microservices

[@kirankumarsukumar]

Great. Holly made it awesome

[@dylam9509]

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.