News for hackers. Stuff that matters.
Re:You Want Modules, Not Microservices by gadflyinyoureye on Tuesday January 03, 2023 @05:48PM (#34239265)
Sometimes. If the services are all interrelated, you’re as dead on the water with Microservices was you would be in a monolith.
Re:You Want Modules, Not Microservices by threeseed on Tuesday January 03, 2023 @06:35PM (#34239713)
You design your microservices so that they gracefully degrade.

So if a database service is not available you simply return stale, cached data until the service is back up.

Re:You Want Modules, Not Microservices by mixermachine on Tuesday January 03, 2023 @06:13PM (#34239510)
Sure depends on the architecture. When the auth service is down, everything else should be down. But when the "optional feature" service is down, a core component should be unaffected by that.

Split up services where it makes sense and don't over do it. That's how I design my projects.

Re:You Want Modules, Not Microservices by varsketiz on Tuesday January 03, 2023 @07:04PM (#34239953)
For many websites, there is considerable amount of content that should be available if auth is down. Think eshops, news portals, etc.
Re:You Want Modules, Not Microservices by vinay_ys on Wednesday January 04, 2023 @08:42AM (#34245396)
When the auth service is down, only new authentications should fail. Existing auth sessions should continue to function just fine. This exact failure mode occured at Google in early 2021 which caused a fairly big outage but not as big as it could have been because of this design choice.