2 ms·
I worked at a hybrid shop that had main MySQL and MongoDB databases on bare metal rented servers and all the new extra features/services built in AWS. It was a
by karmakaze 4y ago
I worked at a hybrid shop that had main MySQL and MongoDB databases on bare metal rented servers and all the new extra features/services built in AWS. It was a pretty good split. We did have some human cost in handling hardware failures and scaling of the hardware but it was way less than cloud hosting for that much CPU and RAM would have been as well as access to higher performance machines. I'm glad that most of the infrastructure handling scripts in Ansible and Chef were made before I got there and only had to make a few new specialized ones.
- lastofus 4y agoI’d think the latency between the app servers and the DBs would be a problem, given they didn’t live in the same data center. How was that mitigated?
- karmakaze 4y agoOh right, we did have many app servers located with the DBs as well. They were stateless and numerous so could be anywhere. The datacentre with the bare metal did have dedicated links to the nearby AWS region we were using. At one point I think one of their redundant links got severed on purpose by accident, so things were slow for a while. The microservices in AWS were feature-services that had their own datastores so only paid a single overall request latency than the many app-server to db queries per user request.