Everyday noise is all around you.
From private to public cloud, multi-cloud and even hybrid cloud, you are inundated with information telling you that this is the way to your digital future. To complicate matters while considering these choices, you are expected to maintain your day-to-day tasks of improving the user experience and agile delivery of these applications.
Wrapped up in all of this delivery and architectural infrastructure, there are numerous data decisions to consider when engaging with any cloud experience. There are regulatory and compliance pressures that force you to evaluate how we collect, process and store our surveillance data. Understanding the pitfalls surrounding the collection, maintenance and storage of your cloud data can mean the difference between failure and success within your cloud strategy.
This series is based on a speech previously given in Dublin, Ireland, and discussed with a good friend of mine Roel Hodelmans. Audience reactions inspired me to share the concepts in this series.
The first article in this series provided an introduction to the cloud and data, what it means in a cloud-based architecture beyond simple storage. The second article in this series talks about the forgotten data that is often overlooked when planning cloud solutions. This third and final article explores a new operational role that will be most important in your organization.
FinOps is the decisive operation
Many of us are re-architecting our applications and development processes to be cloud-based, our operations to be platform providers, and building a Site Reliability Engineer (SRE) organization to close the feedback loop between platform users and providers. We’re talking (I hope) about data portability, having exit strategies and baselines. We talk about security and we talk about usability.
The one thing that is often overlooked is who owns the decisions that are made about observability, data and cloud providers. Naturally, the ultimate responsibility rests with the CIO, as you might imagine, but often at lower levels we see developers, DevOps, architects, and others making decisions that have serious cost implications.
In the previous article you saw the growth of observability data is out of control in this quote shared here to refresh your memory.
“It’s remarkable how common this situation is, where an organization pays more for its monitoring data (typically metrics, logs, traces, and sometimes events) than for its production infrastructure.”
Recently, IDC (2022) published a cloud report in which it shared an amazing revelation showing that companies are taking this issue seriously.
“By 2023, 80% of organizations using cloud services will create a dedicated FinOps (financial operations) function to automate policy-driven visibility and optimization of cloud resources to maximize value.”
The action taken is almost universal and aims to resolve cost issues by placing a financial owner to drive decisions and processes in your organization.
The pitfalls of cloud data
The three pitfalls covered in this series covered cloud and data, not just storage issues, but showed how data visibility is often ignored in cloud solutions. Finally, the role of FinOps will emerge in your native cloud world in the very near future to handle the ownership and management of processes to gain control over natural cloud observability and data issues.
This series provides an overview of the original session presented live in Dublin and hopefully has been able to share awareness of the pitfalls that may be in your way with cloud solutions and your data growth as a result.