4 ms·
Basic replication is maybe close to what you could call solved, but I'd say that there's still complications like georeplicating multi master write machines are
by pcnix 8y ago
Basic replication is maybe close to what you could call solved, but I'd say that there's still complications like georeplicating multi master write machines are still quite complicated, and need a dedicated person to manage. Hiring being what it is, it might just be easier to let Amazon hire that person for you and pay Amazon directly.
I see cloud services as a proxy to hire talented devops/dba people, and efficiently multiplex their time across several companies, rather than each company hiring mediocre devops/dba engineers. That said, I agree that for quite a few smaller companies, in house infrastructure will do the job almost as well as managed services, at much cheaper numbers. Either way, this is not an engineering decision, it's a managerial one, and the tradeoffs are around developer time, hiring and cost.
- stephenr 8y ago> I see cloud services as a proxy to hire talented devops/dba people, and efficiently multiplex their time across several companies It's only a proxy in the sense that it hides them (the ops/dbas) behind a wall, and you can't actually talk directly to them about what you want to do, or what's wrong. If you don't want to hire staff directly, consulting companies like Percona will give you direct, specific advice and support.
- scarface74 8y agoIf something goes wrong, we can submit a ticket to support and chat/call a support person immediately at AWS. We have a real business that actually charges our (multi million dollar business) customers enough to pay for a business level support. But in your experience, what has “gone wrong” with AWS that you could have fixed yourself if you were hosting on prem?
- scarface74 8y agoBasic replication is maybe close to what you could call solved, Locally hosted basic synchronous read replicas are a solved a problem?