Introduction
As a pioneer in cloud computing, Amazon Web Services (AWS) transformed the tech landscape, enabling startups to launch without cumbersome physical infrastructure. I was among the first to evangelize AWS, even organizing events to spread the word. Yet, after 15 years of loyalty, I left the ship. Recently, returning to AWS reminded me starkly of why I left.
The Rise of Cloud and AWS
AWS started with services like S3, EC2, and SQS, promising a revolution in managing IT infrastructure. For entrepreneurs, it was a godsend: no more expensive and complex data centers. But behind this innovative facade, problems accumulated.
The Accumulating Annoyances
Lack of Client Libraries
In its early years, AWS let the community develop client libraries, a decision that cost developers their evenings and weekends. This outsourcing of basic work eventually wore down many professionals.
Delayed Transition to Python 3
AWS's slow adoption of Python 3 frustrated developers who had to deal with an outdated language. This delay raises questions about AWS's responsiveness to technological changes.
Hidden Costs
DynamoDB and Prohibitive Pricing
Using DynamoDB can be costly, with unpleasant billing surprises. For instance, a simple test can result in a $75 USD bill in a single day. Data egress pricing, once at 20 cents per gigabyte, remains considered excessive at 9 cents today.
Billing Complexity
AWS's billing is a real headache, with hidden costs related to internal data movements. This complexity requires deep expertise to avoid financial traps.
IAM and Overall Complexity
The Identity and Access Management (IAM) system is one of the most bewildering. Its complexity is such that even advanced users get lost. This complexity isn't limited to IAM; it's pervasive throughout the AWS architecture.
Conclusion
Returning to AWS reminded me why I chose to leave. Despite its invaluable contributions to cloud computing, the challenges it poses can erode the trust of even its staunchest advocates. It's crucial to weigh the pros and cons before fully committing.
Let's discuss your project in 15 minutes.