MY EXPERIENCE WITH AMAZON WEB SERVICES
Back in 2016 when I wanted to set-up a single unit cloud windows server for a client to run his workload outside his work station as he goes on vacation. Well, you probably guessed right, I had other solutions but those do not fit into the requirements I need to fulfil this request. I headed to google to do the usual. Perhaps, I didn't structure my search very or AWS then didn't bother to do SEO on the particular query I was interested. I took a while before AWS showed up in the search amongst other services of course.
Well, the introductory descriptions caught my attention and I quickly hopped in to get done what I need to only to behold a wonder as I signed up and signed in. I began to wonder, HOW ON EARTH DO THESE PEOPLE (AWS) EXPECT THEIR USERS TO WORK WITH THIS? Honestly, for a short while, I felt like I have stumbled on a website made for aliens and I need to get out of here quickly before it gets uglier.
I guess what I saw was out of normal for a windows user, and might rather be simple for a Linux user which I was not back then in 2016. Well, to cut the long story short, I will be discussing my experience in this article under two distinct categories. The billing, and service reliability.
The billing.
When it got to understand the cost of initiating the service, I felt like I needed to take a master class just to understand what is going on. At some point, I felt there isn't any pattern to this, the site just milk money from your linked account as it so pleases and that was the height of it. I was so totally fed up with having to deal with some series of technicalities that consumed up my time from just running a very simply workload on a service (AWS) that is supposed to provide me a solution to the problems I came to solve. Technically, this would be stated as the complexity of working with the billing set-up greatly increased the general overhead of running the service hence reducing productivity.
The service reliability
I wouldn't know if what I experienced in AWS was their definition of standard as if it is? Then, my guess is standard is a very relative term.
It was classically horrible. For example, to ensure I don't go over the top with my resource usage, I only ran only one application in the server.
The service setup was being a nightmare in numerous ways: with no downtime notification, I would sign into my server and behold, my server is down and my application is offline for "who knows when". I kept restarting and troubleshooting often and often that it almost accounted for a business process entirely. The network connection was fast but latency was large. In the long run, I looked back at the time spent on the platform AWS, recounted a lot of flaws and though to myself, are they just riding the cloud space with no worthy competitor to close up on their gaps and deliver a better service.
In summary, the services were not user friendly, and the billing was like someone reaching out his hands into your pockets without restriction. For poor service, the bills became annoying.
Post a Comment
If you can't commemt, try using Chrome instead.