5 ms·
Ah, yes, I’ve felt the pain of an unnecessary microservices migration. It ate time for years and the core was still a mess
by lars512 4y ago
Ah, yes, I’ve felt the pain of an unnecessary microservices migration. It ate time for years and the core was still a mess
- anticristi 4y agoI think people really exaggerated with the microservices trend. Today, I recommend to keep code in the same executable unless there is a good reason not to. Good reasons include: - Stateful vs stateless: databases and message queues should be your first (hopefully off-the-shelf) "microservices". - Different lifecycles: API serving vs background task - Different security needs: Frontoffice vs Backoffice code - Different teams: But make sure to introduce a clear customer-vendor relationship.