2 ms·
Do you get the cross AZ redundancy? and you’re managing more servers and probably spending more than just using an ELB. What about the HA from the target server
by scarface74 7y ago
Do you get the cross AZ redundancy? and you’re managing more servers and probably spending more than just using an ELB. What about the HA from the target servers? If you were using a load balancer + autoscaling group with a min/max of 2. If your server went down or your entire AZ went down, autoscaling would bring another one up. If the server or AZ went down running your load balancer, it would also be redundant?
One of our web servers crashed in the middle of the night once. I got an alert saying it crashed and that another one was brought up. I turned over, went back to sleep and investigated the next morning. If the “server” running an ELB crashed, I wouldn’t have to care.
Do you really think that you’re going to be changing providers Willy nilly once you reach any type of scale?
It’s just like all of the bushy tailed “architects” who use the repository pattern just in case one day their CTO on a whim decides to move their six figure a year Oracle installation to Postgres.
What business value is being added by going through all of the trouble of staying “cloud agnostic” compared to the lack of HA and maintenance.
Btw, we also don’t have to manage Jenkins servers. We have a cloud formation template with parameters and quick create link that a developer can click on to create a CodeBuild project anytime they want to create a new build project. They specify the Github link that triggers the job. You then specify your build steps as a list of bash (Linux) or Powershell (Windows) commands in a yaml file.
We could also do the same with CodePipeline - create a CF template that creates Code Pipeline jobs on the fly, but we do use OctopusDeploy for deployments.
CodeBuild runs Docker containers to run builds. Again no servers to manage but I believe by default it can run 50 builds simultaneously. If a build job needs custom tooling or a custom version of a runtime, the developer can build a custom Docker container to run the build.
You’re doing more work just in the eventuality that you may want to rip out your entire infrastructure and you’re paying more for the privilege.
- arminiusreturns 7y agoYou've obviously fully bought into AWS and don't want to hear anything to the contrary. That's fine if it works for you, but you aren't interested in honest conversation, so I'm done here.
- scarface74 7y agoIt’s not about “fully buying into AWS”. I would say the same about Azure or GCP - well not GCP I wouldn’t trust Google for any infrastructure. If you have a static workload and the staff to handle infrastructure, AWS may not be worth it. Use a colo or a cheaper service like Linode. Everything I use managed services for I’ve done on prem. I’m saying that it is just as much a waste of money and time to use any cloud provider just to duplicate what you could do at a colo. I would say the same thing about spending extra money for Oracle or SQL Server. Why spend extra on a commercial solution and not take advantage of it. You wouldn’t use Excel just to create CSV files.
- arminiusreturns 7y agoI come from places where that have self-managed on-prem datacenters, with self-managed CPU/GPU clusters, and using CloudFormation for internal infrastructure simple is a non-starter, but with some stuff in AWS, why would we do half CF and half terraform? Do it in tf et al for both. Yes I have occasionally used ELB/EFS in front of HAproxy for some of the reasons mentioned, because I recognize some situations where the value-add is worth the tradeoff. The entire point of my post is that lock-in to AWS can be bad in certain situations, which I have tried to clarify multiple times now and you have ignored every time. I'm not saying it's bad in all situations, just that it can be bad in some. Your extreme defensiveness seems strange to me for that reason. I look at it like datacenter design. You don't have just one isp. You have multiple ISP lines incoming, often in different forms (aerial/underground/wisp) so that you are never too dependent on one thing. Your metaphorical datacenter may have a OC-3840, and that may be a big feature for you, but you should at least admit to yourself and customers not having other ISP lines might be a weakness, despite the awesomeness of the 3840..