You Need a Multi-Cloud Dashboard Because I Want To Sell You One


If I called you and told you that your gasoline budget should be on the same dashboard as your movie ticket budget, you’d look at me like I just laid an egg.
Why, then, do so many companies insist you need to view your GCP, Azure, and AWS spend in the same dashboard?
Different cloud providers run different workloads for your business (or at least they damn well should!) because multi-cloud for a given workload is invariably the wrong move.
I go into this in some depth elsewhere. But today’s post is less about the poor strategic decision itself than it is the idea of having a dashboard to centralize all of your public cloud spend in the same context.
When you’re using multiple providers, the billing dimensions are different, the confusion levels are similar, and there’s no direct comparison that makes sense at a resource level. CPU and RAM options alone vary to a point where it’s very hard to get 1:1 equivalence between instances (or virtual machines) across providers, so you’re rounding. Invariably, you’re rounding badly.
Your CFO doesn’t care what you’re spending on container orchestration. They care how big the checks you’re writing to AWS and Azure are, how much of those checks are for development versus production, and what those numbers are going to look like 18 months from now.
The comparisons that can be exposed and shown via API aren’t the things that are relevant to a business context—and business context is something that cloud visibility dashboards are completely lacking.
To wit, everyone’s got a metric for 500 errors. But nobody’s got a metric for how happy their users are.
It turns out there’s no API for business insight.
My perhaps overly cynical take is that the companies selling these multi-cloud solutions have a vested interest in customers making suboptimal cloud decisions.
If you go all in on a single cloud provider, the right dashboard answer is either “the one they provide for your use” or “picking up the phone and yelling at them until the dashboard they provide for your use meets your needs.” It’s not cutting large checks (or worse, a percentage of your cloud bill!) to third-party companies that are selling a solution for a problem you almost certainly don’t have.
What’s worse is that as native dashboards continue to improve, third-party vendors become actively incentivised to encourage and promote multi-cloud strategies that actually  harm their customers.
I remain steadfast in my opinion that a big driver behind multi-cloud discussions is a sea of vendors who depend on you making a poor decision. Otherwise, they have nothing to sell you. [Source]-https://www.lastweekinaws.com/blog/you-need-a-multi-cloud-dashboard-because-i-want-to-sell-you-one/
AWS Training for Beginners Courses in Mumbai. 30 hours practical training program on all avenues of Amazon Web Services. Learn under AWS Expert


Comments

Post a Comment

Popular posts from this blog

Why, when and how to return Stream from your Java API instead of a collection

Introduction Collections are basic and commonly used data structures. Programmers from the beginning of their career learn how to use them to receive, process and return data. Getting more advanced in Java programming, they find stream() method to convert a collection into a stream and learn how to process data using some of the stream’s useful methods like map, flatMap or reduce. They could also notice that other APIs in Java return a stream too e.g. String.lines(), Matcher.results(), Files.find(), Random.ints(). If you have experience with consuming streams but haven’t produced them yet, this article is for you. I’m going to show you some scenarios where streams can be very convenient and examples on how to use them. Additionally, I shortly mention error handling and resource management. The article is based on standard Java library java.util.stream. It’s related neither to reactive streams nor to other implementation of streams like e.g. Vavr. Also, I’m not going to cover a...
Read more

What is Kubernetes?

Kubernetes (also known as k8s or “kube”) is an open source container orchestration platform that automates many of the manual processes involved in deploying, managing, and scaling containerized applications. In other words, you can cluster together groups of hosts running Linux containers, and Kubernetes helps you easily and efficiently manage those clusters. Kubernetes clusters can span hosts across on-premise, public, private, or hybrid clouds. For this reason, Kubernetes is an ideal platform for hosting cloud-native applications that require rapid scaling, like real-time data streaming through Apache Kafka. Kubernetes was originally developed and designed by engineers at Google. Google was one of the early contributors to Linux container technology and has talked publicly about how everything at Google runs in containers. (This is the technology behind Google’s cloud services.) Google generates more than 2 billion container deployments a week, all powered by its ...
Read more

Best way to learn Java programming

Having said that I am writing this post dedicated to all my young (or I should say beginner) fellows who want to attain a certain level of proficiency in java technology and somewhere would like to take my advice on this. Keep in mind that if you do not like the way to learn java, I am proposing in this post, then just ignore me. Period. OR better, suggest me what you think is the better way to learn java fast or easily. Here I am assuming the people reading this post will be, who are very new to language, so I will start by listing first thing first. Make sure you have prepared your Java development environment ready i.e. You have installed JDK/JRE and you have an IDE like Eclipse. 1) Learn the language basics This is the first step for very obvious reason. If you don’t know the basics then you will never know either what to do next or what you are doing wrong. Initially, I do not expect from you to become the master of all java basic stuffs like keywords, core concepts o...
Read more