2 ms·
Microservices became this mess because people only think about production. Nobody builds microservices as standalone units that should be testable and runnable
by phendrenad2 4y ago
Microservices became this mess because people only think about production. Nobody builds microservices as standalone units that should be testable and runnable in isolation, with ZERO external data. Instead, everything relies on everything, so it's just a monolith split up into microrepos. Worse, people have started putting app configuration in S3 and other dumb things (I've seen it...) do you cannot run things locally, or even match production unless you have AWS creds. Madness.
- TimTheTinker 4y agoMicroservices should indeed be able to run in isolation, but that doesn't remove the need for end-to-end and integration testing. At a minimum, the product owner should be able to try out the new feature in the UI without having to deal with a staging environment.
- gedy 4y ago> Nobody builds microservices as standalone units that should be testable and runnable in isolation, with ZERO external data. Instead, everything relies on everything, so it's just a monolith split up into microrepos. Yeah this is the surprising thing to me - I've worked with otherwise bright people but whenever we've introduced services/microservices, it seems the default reaction is to just make a "distributed monolith" with circular dependencies and tight coupling. I'm only half joking that 90% of my "architect" role is just point out we shouldn't have circular dependencies.
- codethief 4y ago> Instead, everything relies on everything, so it's just a monolith split up into microrepos …and with added network calls! > Microservices. grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too. seem very confusing to grug (Source: https://grugbrain.dev/ https://grugbrain.dev/)