3 ms·
Scale the whole thing. The cost of doing that is usually orders of magnitude less than the true CapEx and OpEx of microservices. edit: If breaking out one serv
by sagichmal 6y ago
Scale the whole thing. The cost of doing that is usually orders of magnitude less than the true CapEx and OpEx of microservices.
edit: If breaking out one service from your monolith worked for your use case, that's great. I'm not trying to deny your experience. It is atypical, however.
- scarface74 6y agoWe are talking about a 16x difference in resources. Would you also suggest scaling a database that was more read heavy than write heavy instead of splitting reads and writes when you can deal with eventual consistency and just autoscale the read replicas?
- sagichmal 6y agoThe comparison is not equivalent.
- cutemonster 6y agoAgreed, I think the comparison is not equivalent, because a read replica actually is the same database application (same "monolith") just started with different parameters, to behave as a replica
- scarface74 6y agoThe database is the same but you have to then separate your code into reader and writer services with different connection strings, you have to make sure that anything that can’t be eventually consistent uses the writer connection string, etc. It’s not just a matter of spinning up a database. Also, since many enterprise apps live stores procedures and putting business logic in the database, that’s another ball of wax you have to untangle.