4 ms·
A bit of a translation barrier so I'm not positive but the company advocating this appears to be an agency that builds things for multiple clients. For that cas
by kevan 6y ago
A bit of a translation barrier so I'm not positive but the company advocating this appears to be an agency that builds things for multiple clients. For that case it makes more sense to split out capabilities like that so they can easily pull them in like Lego blocks to other projects. For everyone else I'd advocate starting with a monolith until you need to split things.
- mdoms 6y agoMakes sense for whom? Maybe for them, certainly not for their clients.
- ragona 6y agoIf the firm is fast and produces reliable platforms at the cost the client is looking for then their clients couldn’t care less whether it’s Django (sigh) or Lambdas.
- rumanator 6y ago> Makes sense for whom? Maybe for them, certainly not for their clients. It makes sense for the system, and thus for the client. Just because there are a lot of boxes in the diagram that does not mean the system is complex. A lambda is just a stateless message handler. Half the diagram are lambdas. The rest is just a few persistence services and then stuff related to external interfaces, likr DNS services and API gateways and auth and pubsub. Any desktop app is way way more complex than this. A dialog box has easily twice the number of handlers.