Abstract
In this session, we delve into the concepts of FinOps and Cost Optimization, providing important considerations to aid in the successful implementation of a robust Cost Optimization strategy. We will explore various techniques to optimize your cloud expenditure and highlight common pitfalls that should be avoided.
Sponsored session
Session Sponsored By
DoiT is a global multicloud innovator that helps simplify the most important cloud challenges to optimize use and accelerate return.
76%
senior dev or higher
1:11
speaker ratio
60+
practitioners
QCon London 2024 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Sponsored Solution Track IIFrom the same track
Tuesday 9 April
10:35 Westminster (4th Fl.) Sponsored Why You’re Doing Service Catalogs Wrong Lisa Karlin Curtis Founding Engineer @Incident.io Service catalogs promise a lot of things: powerful automations, insights into your technology estate. But over the last few years, many of us have learned that setting up and maintaining a service catalog is **really hard**. 11:45 Westminster (4th Fl.) Sponsored Driving Down the Cost of Observability Chris Cooney Developer Advocate @Coralogix Ten years ago, observability barely existed. Now, observability costs can equal 10%–30% of operational budgets. Inefficient observability has become a blocker to a scaled DevOps strategy. 13:35 Westminster (4th Fl.) Sponsored FinOps & Cost Optimization: Considerations on Implementing an Effective Strategy Louis Muller Senior Data Analytics Architect @DoIT In this session, we delve into the concepts of FinOps and Cost Optimization, providing important considerations to aid in the successful implementation of a robust Cost Optimization strategy. 15:55 Westminster (4th Fl.) Sponsored Specs Generation, Bring Intelligence in your API Management Strategy Rémi Sultan Senior Software Engineer @Gravitee In an era where access to data is In today's tech realm, maintaining a solid API setup is crucial. Yet, with the array of technologies and standards like OpenAPI and AsyncAPI out there, things can quickly get messy. Wrangling all your documentation into one coherent package?