Patryk Golabek
CTO/Software Architect at Translucent Computing Inc
Since we’re running it ourselves, it's our own flavor of MySQL, for dev, and QA, staging, production environments, that cost is basically a part of their running between this cluster. So I can't give you a fixed cost, but I can give you the cost of the entire cluster. There are many nodes in a cluster, and there's many different parts continuously running it. So to fully utilize the cluster, we put everything in it and just try to maximum each node. So you can have a MySQL database beside a Java Microservice and Angular applications on the same node, and using the same kind of resources. So it would be difficult for me to kind of break it down. Obviously I'll do a deep dive, and I'll look at it, in terms of, what percentage of the CPU is being used by MySQL. Now when it comes to the Cloud versions, obviously there's a fixed cost with that. So for example, one of the clients uses our database, they chose to go with the extra large version of the ECQ's, and there's a price for that. And you can just get a price quickly, and there's a whole chart of pricing there. So that's based on clients and their comfort level. We can tell them exactly what performance we're requiring here, and then say, what is the minimal thing we need here, in terms of CPU resources and connections? So that's what you really need for just a cloud version of it. Once we define that, then we tell the client, this is what you really need. You can get away with a smaller version of the virtual machine by using something bigger. To be comfortable they decide to do it. So I'm dealing with the pricing, and the pricing is transparent. I have all the separate pricing for the databases as well. And from that, you can figure out what the cost is. There's no licensing fees here because it's open source. So the only fees are really just for using the Cloud resources, even if you go with managed or non-managed, you're still using the Cloud resources. You can be more frugal if you're running it yourself, versus what Google or Amazon will do for you. It'll be a little more pricey to go with them, but because it's a managed solution, you do have that peace of mind, because they're managing it for you. You just connect with it and just talk with it. But in our cases, we deploy it, we manage it, we back it up, we do all that stuff. So there's more work that we have to do, but a lot of time we eat up the cost because it's not an expensive thing to do. So it can be more cost effective running within the Coud, than in a non-managed version, self-hosted version. At the end of the day, Google and Amazon are still making money, because it doesn't matter if you're running it yourself or it's managed, it's still using the Cloud. It's the same CPU and same RAM. View full review »
Partner at a tech services company with 51-200 employees
60% ROI (There are DLs — direct labor costs and overhead costs, but once it is set up, we image the configuration and deploy our designs in docker). View full review »
Learn what your peers think about MySQL. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,052 professionals have used our research since 2012.