Remix.run Logo
Gud 2 hours ago

Do you believe "micro services" can make a comeback? local daemons with an exposed API, each daemon vibe coded?

layer8 22 minutes ago | parent | next [-]

Microservices are about separate deployment. Regarding separating the development/maintenance of components, you can achieve that in a monolith by composing it out of corresponding modules/libraries with defined APIs. That’s good practice anyway.

swiftcoder 2 hours ago | parent | prev | next [-]

Unless we are planning to deploy them all individually to an expensive serverless platform like Lambda, the coordination challenges and overprovisioning are going to more than outweigh whatever architectural benefit you reap (in human-centred development, micro services are solving an entirely different problem - Conway's Law)

jdlshore an hour ago | parent | prev | next [-]

Microservices don’t reduce complexity, they just move it to the interactions between services. You have the same fundamental design problem.

In other words, if you can’t design a modular monolith, you can’t design a set of microservices.

throwaway27448 an hour ago | parent | prev | next [-]

Sure, why not? The same reasons they succeeded originally will work just as fine now.

stavros 2 hours ago | parent | prev [-]

Please no.

jambalaya8 2 hours ago | parent [-]

Lemme guess, you were in favour of monolithic systemd too?