I’ve been blogging since 2005.
I hope you enjoy what I find interesting enough to write.
When I first heard of Alex Xu’s System Design Interview – An insider’s guide, my reaction was “finally someone wrote a book with deep discussions around scalable systems design”, so I purchased it.
tl;dr: If you are new to systems design and uninitiated in distributed systems space, this book should be an instant buy for you. If you are seeking answers to how Facebook scales, how APIs like AWS S3 work or want to learn trade-offs around distributed databases and queues, this book might leave you unsatisfied as it seems to be focused on getting the beginners to succeed in the interviews. Read More →
I’m continuing with these articles on Cloud Run REST API that nobody really needs to read. This time, I’m back with a Go code walkthrough that shows how to deploy and manage services in Cloud Run through its Go API client library.
Cloud Run already offers deployment via mainstream method like CLI, web UI, IDEs and Terraform. So this article is dedicated for the <%0.1 of Cloud Run users (a.k.a. the ones keeping it real) out there who needs to use Cloud Run API with Go. Let’s begin. Read More →
Today I’m open sourcing runsd, an unofficial DNS service discovery and authentication layer I’ve built for Cloud Run to make microservices networking easier.
If you’ve used Kubernetes or Docker Swarm to run microservices, then you are
probably familiar with the concept of DNS service
This lets you call another service as easy as connecting to
Your request will be routed to a container running the service named
even if it’s on another machine on your cluster.1
However, Cloud Run currently does not offer a DNS service discovery experience and authenticating private services on Cloud Run requires you to make code changes which makes your services less portable (we’ll talk more about this soon). Read More →
Last month Google introduced GKE Autopilot. It’s a Kubernetes cluster that feels serverless: where you don’t see or manage machines, it auto-scales for you, it comes with some limitations, and you pay for what you use: per-Pod per-second (CPU/memory), instead of paying for machines.
In this article, I’ll do a hands-on review of GKE Autopilot works by poking at its nodes, API and run a 0-to-500 Pod autoscaling to see how well it scales from a user’s perspective.
I’ve published documentation on best pratices for running WebSockets applications such as chatrooms or game servers on Cloud Run’s stateless environment.
Cloud Run now supports WebSockets (and gRPC streams!) so I wrote a best practices guide for you to architect your streaming apps properly in a serverless world.https://t.co/MMJNhsbUVS pic.twitter.com/tu7msYtH0Z— Ahmet Alp Balkan (@ahmetb) February 19, 2021