>When done well they are supposed to help, but in reality I only see systems that can work when all microservices are up and responsive; if one is down, the ent

>When done well they are supposed to help, but in reality I only see systems that can work when all microservices are up and responsive; if one is down, the entire thing is dead. Why didn't you make a monolith? There are different kinds of microservices, some are infrastructure critical (for example, we have an auth service, if it goes down the whole thing goes down because users simply can't login anymore - and it doesn't matter if it's a microservice or a monolith, the end result is same), others are not so critical, for example we implement additional product modules (purchased separately) as microservices which have their own SPAs so if they go down basically only one page becomes unavailable and the system as a whole is unaffected. Microservices aren't necessarily about 100% SLA, they help scale teams and deployment (however I'd say it only makes sense in larger organizations).