Posted inExperience / Information Technology / Investing

Companies That Don’t Use AWS Made More Money Yesterday

AWS (Amazon Web Services) had an hours long outage yesterday. This is the product used by companies that don’t try very hard. You hire the cheapest labor found anywhere and use Agile because they are all just hacks, most of whom never went to college. This service is so unreliable that Down Detector usually has a chart looking something like this.

My neighbor laughed when he read this post asking what AWS customers would do when Amazon went out of business, well, I was ahead of the curve on this call. Amazon reported almost no profit and slowing growth. All the analysts are now talking about Amazon’s slowing cloud-computing sales. Gee, when you have shit service, people stop paying for it.

The Agile Debacle

You cannot use Agile to create reliable things. You have to architect API’s (Application Programming Interfaces) not hack out incompatible versions hour by hour. There is obviously not a qualified Software Architect or Systems Analyst working at Amazon or any AWS customer. No, that’s not a frivolous statement.

No single point of failure.

People who go to college and get actual degrees in Computer Information Systems have the above mantra drilled into our skulls pretty much every day. In our professional lives we speak it as a talisman against failure while reviewing system flow diagrams and SDLC documentation. It is inconceivable to us that any company expecting people to pay money for something would put in the field a system knowing it has a single point of failure.

Enter the AWS customers, where Amazon is their single point of failure.

Amazon, a company with over 125 physical data centers that still cannot design a proper system.

Agile means you don’t create a full SDLC up front. There is no architecture. There is no design. Just a bunch of off-the-shelf stuff that might sorta work held together by duct tape and bubble gum.

Were you gullible enough to buy into that? Nothing that has multi-hour outages can claim to be mission critical. How about your pacemaker not working for a couple of hours while you are out in the sun? Your insulin pump? Your infusion pump for that chemo you have to have at specific intervals?

Roland Hughes started his IT career in the early 1980s. He quickly became a consultant and president of Logikal Solutions, a software consulting firm specializing in OpenVMS application and C++/Qt touchscreen/embedded Linux development. Early in his career he became involved in what is now called cross platform development. Given the dearth of useful books on the subject he ventured into the world of professional author in 1995 writing the first of the "Zinc It!" book series for John Gordon Burke Publisher, Inc.

A decade later he released a massive (nearly 800 pages) tome "The Minimum You Need to Know to Be an OpenVMS Application Developer" which tried to encapsulate the essential skills gained over what was nearly a 20 year career at that point. From there "The Minimum You Need to Know" book series was born.

Three years later he wrote his first novel "Infinite Exposure" which got much notice from people involved in the banking and financial security worlds. Some of the attacks predicted in that book have since come to pass. While it was not originally intended to be a trilogy, it became the first book of "The Earth That Was" trilogy:
Infinite Exposure
Lesedi - The Greatest Lie Ever Told
John Smith - Last Known Survivor of the Microsoft Wars

When he is not consulting Roland Hughes posts about technology and sometimes politics on his blog. He also has regularly scheduled Sunday posts appearing on the Interesting Authors blog.