Codetown ::: a software developer's community
Why use Amazon's container service?
We all experience a common set of tasks when working in IT shops. Someone gets delegated (voluntold) to the task of working with the System Admin, JBoss/Middleware, Security, and Hardware support teams in configuring a brand new set of servers.
Other times we develop an install instructions for JBoss EAP or a database product like MongoDB or Postgress. Then every developer after the first one has to setup and configure the same set of "things".
Guess What?
Now you don't have to any more. You can create a configuration for a "virtual server" and save that for others to use. So, you may be developing a JBoss EAP instance with your favorite WAR deployed to offer up a web service within a container (Docker Image). Or, you might be creating a database virtual server within another container.
Each developer can pull down your configured red hat virtual instance container with your setting you created. Now everyone has zero configuration cost for having the same exact set of testing servers.
Integrating the WAR deployments is possible with tools like Jenkins.
Running your container on your PC or on "the cloud" (Amazon's servers) is really the same thing. The virtual machine can be deployed and run anywhere.
Try out AWS on your own. The only hitch is yes, they ask for a credit card for their "Free environment". Fortunately for me, I had an american express gift card which worked just in setting up the account.
https://aws.amazon.com/free/?sc_channel=PS&sc_campaign=acquisit...!4422!3!96578667522!e!!g!!amazon%20web%20services&ef_id=V0bibAAABAdqv@jn:20160601174220:s
Comment
do similar by creating local VM's on existing infrastructure
Correct Thomas, you make a good point. If you have existing infrastructure to quickly create and tear down linux vm's, then there isn't much of an advantage. The trouble is we typically face is we create nearly physical VM instances which have a spaghetti factory set of things installed on it by SA experts.
Without trying to sound too much like an AWS salesman:
1) spin up a configuration without the "bare bones minimum" OS and nearly 0 Linux experience
2) deconstruct the configuration and re-construct it on the fly with zero residual configuration on the VM image to mess things up
3) the ability to flip OS versions / JBoss versions / Java versions and re-run your regression test over and over and over
4) software developers do not have to be Linux experts (but fly in with root authority haha)
5) throw away the configurations you don't like (mongoDB or PostGress) when you are done testing them
6) Most importantly for many shops: NO RED TAPE - many shops have rigorous software control board committees and groups.Just the act of getting everyone to agree on a potential configuration can take weeks or months (yes, I've seen this). This can be often the largest issue to preventing software upgrades and sapping your leadership and developer productivity.
If you are a sophisticated shop, you won't require this and you may have Linux / Windows VM image instructions already in place. In that case, this all may be moot.
Elastic load balancing
Take a read into this feature of multiple VM's "running from the cloud". If you are familiar with the fun F5 sprayer configurations and the fun of working with experts, then you might find configuring the elastic load balancing a little more fun and a little less challenging on your nerves. The features look very robust and viable.
I really appreciate the work you did but this was a topic I wanted to read more personal experience with substance. I am still weighing in on AWS and would have liked to have read more detail on AWS EC2. I just get the impression from this we could do similar by creating local VM's on existing infrastructure and create environments from VM images to do basically the same -- w/o the Credit Card! But again, I appreciate the effort.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Google Cloud's automated systems suspended Railway's production account without notice, triggering an eight-hour platform-wide outage affecting 3 million users. The cascade took down workloads across all providers including AWS and bare metal because Railway's control plane was hosted on GCP. Railway is demoting GCP to backup-only status.
By Steef-Jan Wiggers
The engineering team at Meta recently outlined how the company migrated a data ingestion platform that transfers several petabytes of MySQL social graph data daily to improve reliability and operational efficiency. The team used techniques like reverse shadowing and continuous checksum monitoring to ensure zero downtime during the transition.
By Renato Losio
Mallika Rao discusses the hidden risk of evaluation debt in production AI systems, drawing on her experience at Twitter, Walmart, and Netflix. She explains why traditional metrics fail modern architectures, breaks down a five-layer evaluation stack spanning infrastructure and UX, and shares a diagnostic maturity model to help engineering leaders eliminate silent semantic failures.
By Mallika Rao
The Cloud Native Computing Foundation has highlighted a new AI-assisted migration approach that enabled engineers to migrate 60 ingress-nginx resources to Higress in roughly 30 minutes, demonstrating how artificial intelligence is increasingly being applied to modernize Kubernetes networking and gateway infrastructure.
By Craig Risi
GitHub reports cutting token costs in agentic CI workflows by up to 62% by pruning unused MCP tools, swapping some MCP calls for gh CLI, and running daily “auditor” and “optimizer” agents. A token-usage.jsonl artefact and an Effective Tokens metric help track spend across models and spot regressions.
By Mark Silvester
© 2026 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown