Scaling Open Event Server with Kubernetes
summary
Open Event’s server, Android generator, web generator and scrapers run as Docker containers orchestrated by Kubernetes on Google Container Engine; components include Flask, PostgreSQL, Celery job queue and ElasticSearch planned, with Android builds isolated into job workers. Kubernetes provides self-healing rollbacks, services for load balancing, and autoscaling (example: spawn another web pod when CPU > 50%). The entire ecosystem deploys from configuration files in minutes and the public deployment runs on a three-node GKE cluster.
AI-written summary · about
chapters (6)
- 0:00Start
- 10:53Horizontal Scaling
- 11:22Self-Healing
- 12:48Storage Orchestrations
- 13:31Predictable Deployment
- 15:06Pod
related talks
37mKEDA: Unlocking Advanced Event-Driven Scaling for Kubernetes
36mAutoscaling Search and Analytics in Kubernetes: The OpenSearch Operator Advantage
32mScaling Multiplayer Game Servers with Kubernetes
36mKEDA: Event Driven and Serverless Containers in Kubernetes
14mOpen Source Ecosystem: Building Sustainable Solutions with Kubernetes
48mEvent-driven serverless architectures using Knative and Cloud Run.
29mUnleashing the Power of Serverless on Kubernetes with Knative, Crossplane, Dapr, KEDA, and Friends
39mOperating OpenSearch at Scale With Kubernetes Operators: Lessons Learned and Community Insights
