There is no doubt that you've seen the use of the mathematical operator <= meaning 'less than or equal to' at the other side of the equation. The reason that this is important is that it relates to the assigning of application SLA (Service Level Agreement) metrics to your applications.
We've all been there. You have some build document or a guidebook for deploying your application or VM or a server of some kind. You've seen it so many times that you're pretty sure that you've memorized it. The problem is threefold:
Anyone who operates highly scalable infrastructure will know that there is one maxim that they must abide by:
This industry is often filled with this notion that we have to replace one technology with another. I can't stress enough how misguided this is as we think about what the role of any technology is in our organizations. The role of technology is to solve a particular challenge or set of challenges for the business. Business could mean selling things, buying things, education, research or anything in between. Technology of the sake of technology will most likely fail in its adoption lifecycle.
The pundits on both sides of the public cloud vs private cloud debate have been touting the strength and longevity of each side. Is there really an option for both to survive with strength in the coming years as public cloud gains massive momentum? This is the ultimate question as we look towards when the tipping point could be for public clouds to write the epitaph of private cloud offerings.
There are many harsh learnings that we experience during significant disruptions and performance issues. The public cloud seems to have been the catch-all answer for solving some of these challenges, or so it would seem. The reality of the public cloud is that it solves specific challenges in a way that has become widely embraced. There are also still a lot of shortcomings and challenges that are in place.
So, your site is down because AWS S3 went away. Too soon? It's never too soon to talk about why the responsibility for designing resilient infrastructure belongs in your camp. It's like when Smokey the Bear used to say that "only you can prevent forest fires". The difference is that it's Jeff Bezos saying it this time.
It's very interesting to see how the real-world implementations of a product or platform happen. One of the more hotly debated IaaS environments around the size and success as an effective solution, is OpenStack. As a huge advocate for the open cloud platform, OpenStack is something that I've spent a lot of time working on from the community side, and with my day-to-day work.
One of the most common questions that I get is "how do you keep learning so many things? Isn't it difficult to always have to learn?" which really made me stop and think about the importance of this question.
Some articles deserve a strong disclaimer. This feels like one of those that deserves a particularly strong one. So, here it goes: