I’m a Staff Platform Engineer at Empathy.co. I mostly manage Kubernetes Clusters, CI/CD orchestration, Elasticsearch, MongoDB and try to break things on AWS, GCP and Azure.
Progressive Delivery in Kubernetes: Analysis
Overview In this post, an analysis of Progressive Delivery options in the Cloud Native landscape will be done to explore how this enhancement can be added in a Kubernetes environment. The most embraced tools from the Cloud Native landscape will be analyzed (Argo Rollouts and Flagger), along with some takeaways
Collaborative Architecture Diagrams
Motivation Architecture diagrams should be visible to everyone in the company, as Trust is one of our principles here at Empathy.co. Ensuring visibility would ensure we have a single source of truth where changes can be tracked and revisions can be made. It would also align Engineering, Growth, and
Cloud FinOps – Part 5: Usage Report
Wrapping up this series, following our previous Cloud FinOps - Part 4: Kubernetes Cost Report, this final piece looks at how to increase visibility of underutilized workloads.
Cloud FinOps - Part 4: Kubernetes Cost Report
This blog post is a continuation of Cloud FinOps - Part 3: Cloud Cost Report [https://medium.com/empathyco/cloud-finops-part-3-cloud-cost-report-865a81c03c1c] , in which we will explore how to gain cost visibility on Kubernetes Workloads. Motivation Nowadays, a lot of companies run their workloads on Kubernetes because there are many benefits to
Cloud FinOps - Part 2: Tag Allocation Strategy
In the first post [https://engineering.empathy.co/cloud-finops-part-1-principles/] of this four-part series, we explored the Cloud FinOps principles and the key milestones in the journey to start walking in FinOps: * Tag Allocation Strategy * Cost Report * Usage Report In this post, we’ll dig deeper into a crucial step in
Cloud FinOps, Part 1: Principles
FinOps, short for Cloud Financial Operations, helps teams optimise cloud costs to get the most value for their projects. Teams adopt best practices and a collaborative culture to manage cloud operations with greater financial accountability: balancing cost, speed and quality. When your teams have problems managing their cloud costs, following
Success story: From AWS EMR to Kubernetes
Motivation This article is an overview of the path we followed to migrate Spark Workloads to Kubernetes and to avoid EMR dependency. EMR was an important support tool at Empathy.co [https://empathy.co/] to orchestrate Spark workloads, but once the workloads became more complex, the use of EMR also