Architecture and Technology First Principles

#23 - Earn People & Leadership Lessons From Hyperscaling Gojek - Ajey Gore

Topic 8 of 14

Published Jan 25, 2021 · Clip 35:00–39:16 (4:15)

Ajey shares architecture first principles: microservices must be asynchronous—synchronous microservices are a sin because you've just split a monolith with an HTTP stack in between; don't do microservices unless you truly need to. He argues languages don't fail to scale—cite Wikipedia (PHP), Facebook (JavaScript), GitHub (Ruby on Rails)—so capitalize on your expertise instead of blaming tech. They moved from RabbitMQ to Kafka and tried gRPC; you need a large message bus but don't chase buzzwords. They stuck with Postgres (beware autovacuum), published a production checklist (e.g., don't add columns to huge tables during deploys), and use each language for what it's built for—Clojure for functional programming, Go for high-speed computation, but Java/Ruby are fine if that's your expertise.