4 ms·
This I feel is the ideal way in many many cases. Only separate out components if the additional cost of service communication (when moving the component away fr
by spacephysics 3y ago
This I feel is the ideal way in many many cases. Only separate out components if the additional cost of service communication (when moving the component away from a monolith) is less than the benefits of scaling/separate repo/etc.
Cost also includes the orchestration and such
- sn0wf1re 3y agoI'm personally a fan of the mono-microlith (or whatever people call it), where you compartmentalize the monolith so that it's a just a flag of what "micro-services" are enabled on each instance. Easy to scale down on a dev machine (one process) and easy to scale out, the local procedure calls just become remote procedure calls (over HTTPS or whatever).