tags / Platform Engineering
46 posts
The closing post of the series. The thread that connects all six patterns, the evolution from glue spaghetti to platform control plane, and why having architectural vocabulary changes how platform teams make decisions.
Hardcoding deployment strategy into pipelines creates a hidden coupling that makes platforms less reliable. The Strategy pattern explains how to make canary, blue/green, and progressive delivery first-class platform concerns.
Every platform connects systems that weren't designed to talk to each other. That connective tissue is glue — and in most platforms, it's 60-80% of what the team actually builds. Here's what glue is, where it lives, and how to design it intentionally.
Pipelines that run kubectl apply directly are automated but invisible. The Command pattern explains why GitOps is architecturally sound — not just a convention — and what you gain from separating the definition of a change from its execution.
Should you expose Kubernetes directly to developers or abstract it? That's not a tooling debate — it's a design question. The Facade pattern and the Golden Path concept explain why your platform's interface is its most important architectural decision.
Manual reconciliation doesn't scale. The Kubernetes controller loop is the Observer pattern at cluster scale. Learn how operators, Argo Rollouts, and External Secrets Operator implement this pattern — and how to decide when to write your own.
Environment provisioning without a clear creation model is slow, inconsistent, and doesn't scale. The Factory and Builder patterns explain why — and what Crossplane, Backstage, and Terraform modules have in common.
Platform engineers apply design patterns every day without knowing it. This series bridges the gap between software architecture vocabulary and the real decisions you make in platform engineering.
bash ml-project/ ├── .git/ ├── src/ │ └── train.py ├── data/ │ └── training.csv 5GB, in Git └── models/ └── model.pkl 2GB, in Git
Terraform, Helm, GitOps... ¿para entrenar modelos? Sí.
"Solo necesito cambiar la variable ENV a 'prod'" - Spoiler: No
Ayer: qué orquestador usar. Hoy: cuándo ejecutar ese orquestador.
Airflow, Kubeflow, Prefect, Dagster: La pregunta que todos hacen mal
Ayer te prometí explicar por qué tus herramientas de Platform Engineering no son suficientes para ML. Pero antes, hablemos de cuando alguien de PE pide automatizar o pregunta si ya esta automatizado,
Hace tiempo, cuando algunos de mis compañeros de datos o de AI (como en ese entonces les conocía) se acercaban y nos pedían infraestructura o forma “despliegues que se salian del standard“, siempre no
Modernizar no es solo tecnología. Es colaboración, criterio y humildad técnica. Reflexiones reales desde la trinchera de plataforma.
Modernizar no siempre es reescribir en Go y meter todo en Kubernetes.
Modernizar todo no siempre es la mejor decisión. Saber qué mover primero puede marcar la diferencia entre el caos y el progreso.
Modernizar no es solo usar Kubernetes o romper monolitos. Desde la trinchera de un Platform Engineer, modernizar significa entender por qué, planear cómo y habilitar el cambio sin poner en riesgo la operación. En este post exploramos las fases estratégicas de modernización y cómo traducirlas en acciones reales desde plataforma, con ejemplos prácticos, herramientas open source y aprendizajes aplicables al día a día.
Welcome to Day 26 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll focus on securing Kubernetes platforms using Open Policy Agent (OPA) for policy enforcement and Trivy for vulnerability scanning..
Welcome to Day 25 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll cover canary deployments and feature flags, two essential techniques for safe, controlled software rollouts in Kubernetes.
Welcome to Day 24 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into autoscaling in Kubernetes, focusing on Horizontal Pod Autoscaler (HPA) and Cluster Autoscaler to efficiently manage workloads..
Welcome to Day 23 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re focusing on secrets management using HashiCorp Vault and AWS Secrets Manager, two powerful tools for securing credentials, API keys, and sensitive data.
Welcome to Day 22 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into Backstage, the leading Internal Developer Platform (IDP) tool, to build service templates and a software catalog for streamlined developer workflows.
Welcome to Day 16 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re focusing on Internal Developer Portals (IDPs) and how to build one using Backstage, an open-source platform that enhances developer experience by centralizing documentation, services, APIs, and deployments.
Welcome to Day 19 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll explore Chaos Engineering, its origins with Netflix’s Simian Army, and modern tools like LitmusChaos, Gremlin, and LambdaChaos that help test system resilience.
Welcome to Day 20 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re doing a recap of observability best practices and assembling a basic observability stack using Prometheus, Grafana, Loki, and OpenTelemetry.
Welcome to Day 18 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into Distributed Tracing using OpenTelemetry, an essential tool for monitoring request flows across microservices.
Welcome to Day 17 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re focusing on visualizing Kubernetes metrics with Grafana, creating real-time dashboards to monitor application performance.
Welcome to Day 16 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll explore Prometheus, the go-to tool for monitoring Kubernetes and collecting real-time metrics.
Welcome to Day 15 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into workflow automation for Kubernetes using Kustomize and Skaffold, two tools that simplify managing and deploying Kubernetes configurations
Welcome to Day 14 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll focus on securing Kubernetes clusters, covering runtime security and policy enforcement to ensure your applications and infrastructure are protected from vulnerabilities and misconfigurations.
Welcome to Day 13 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re focusing on monitoring and observability, key components for maintaining the health, performance, and reliability of your applications in Kubernetes.
Welcome to Day 12 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving deeper into GitOps by exploring Argo Rollouts, a powerful tool for managing progressive delivery strategies like canary and blue-green deployments.
Welcome to Day 11 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into GitOps, a modern approach to managing Kubernetes applications declaratively, with ArgoCD as our tool of choice.
Welcome to Day 10 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll explore how to combine Helm and Terraform, two powerful tools, to simplify the deployment and management of Kubernetes applications.
Welcome to Day 9 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving deeper into Terraform, exploring advanced features like modules, workspaces, and how to manage Kubernetes resources programmatically
Welcome to Week 2 of the Zero to Platform Engineer in 30 Days challenge! 🚀 This week, we’re diving into Infrastructure as Code (IaC) and CI/CD pipelines, two cornerstones of modern platform engineering. Today, we’ll focus on understanding what IaC is, why it matters, and how it helps manage infrastructure efficiently.
Congratulations! 🎉 You’ve completed the first week of the Zero to Platform Engineer in 30 Days challenge. This week, we’ve covered the foundations of Cloud Native and Kubernetes, setting the stage for everything to come. Today, we’ll recap the key concepts, reflect on your progress, and dive into some hands-on challenges to solidify your learning.
Welcome to Day 6 of the Zero to Platform Engineer in 30 Days challenge! Today, we’re focusing on ConfigMaps and Secrets, two essential tools for managing application configurations and sensitive data in Kubernetes.
Welcome to Day 5 of the Zero to Platform Engineer in 30 Days challenge! Yesterday, we explored Deployments and Scaling in Kubernetes, learning how to manage application lifecycles and scale them effectively. Today, we’ll dive into Kubernetes Services, which are essential for enabling communication between your applications and making them accessible to users.
Welcome to Day 4 of the Zero to Platform Engineer in 30 Days challenge! Now that we’ve covered the basics of Kubernetes, it’s time to explore one of its most powerful features: Deployments and Scaling. These tools let you manage your applications efficiently, ensuring they’re always running and able to handle demand.
Welcome to Day 3 of our Zero to Platform Engineer in 30 Days challenge! Today, we’re diving into Kubernetes, the backbone of modern cloud-native platforms. Whether you’re new to Kubernetes or looking to refine your skills, this post will give you a strong foundation to build on.
Welcome to Day 2 of the Zero to Platform Engineer in 30 Days challenge! Today, we’re diving into the fundamentals of containers, the role of Docker, and exploring other container runtimes like CRI-O and containerd. By the end of this post, you’ll know how to build, run, and manage containerized applications.
Welcome to Day 1 of Zero to Platform Engineer in 30 Days! Yesterday, we set the stage with what Platform Engineering is and why it’s such an exciting and impactful field. Today, we’re diving into one of the most important resources for Platform Engineers: the Cloud Native Computing Foundation (CNCF) and its famous Landscape.
Ready to level up? In just 30 days, you’ll go from zero to Platform Engineer hero. We’ll break it down step by step, covering everything from Kubernetes to building Internal Developer Platforms (IDPs). Let’s make cloud native simple and fun!.