EP185: Docker vs Kubernetes
AWS Guide to Cloud Architecture Diagrams (Sponsored)
Enhance visibility into your cloud architecture with expert insights from AWS + Datadog. In this ebook, AWS Solutions Architects Jason Mimick and James Wenzel guide you through best practices for creating professional and impactful diagrams.
This week’s system design refresher:
Rate Limiter System Design: Token Bucket, Leaky Bucket, Scaling (Youtube video)
Docker vs Kubernetes
Batch vs Stream Processing
What are Modular Monoliths?
What is the difference between Process and Thread?
How AI Agents Chain Tools, Memory, and Reasoning?
SPONSOR US
Rate Limiter System Design: Token Bucket, Leaky Bucket, Scaling
Docker vs Kubernetes
Docker is a container platform that lets you package applications with their dependencies and run them on a single machine. Here’s how it works:
Starts with the app code and dependencies written into a Dockerfile.
The build image step creates a portable container image.
A container runtime runs the image directly on the host machine.
Networking connects containers and external services and produces the final running app.
Kubernetes is a container orchestration platform that manages containerized applications across a cluster of machines for scalability and resilience. Here’s how it works:
Starts with the app code and dependencies in a Dockerfile.
The build image is passed to a container runtime supported by Kubernetes.
A master node runs the API server, etcd (key-value store), controller manager, and scheduler to coordinate the cluster.
Worker nodes run the actual containers inside the Pods, managed by Kubelet and kube-proxy for networking.
Produces a running app that is distributed, scalable, and self-healing in nature.
Over to you: Have you used Docker or Kubernetes in your projects?
Batch vs Stream Processing
Data never stops flowing, but how we process it makes all the difference. When building data systems, two main approaches emerge: batch processing and stream processing. Both have their place, depending on whether you need accuracy over time or immediate insights.
Batch Processing: Collects data in chunks and processes it at scheduled intervals, great for reports and historical analysis.
Stream Processing: Processes events continuously in real-time, powering dashboards, alerts, and recommendations.
Batch = high-volume, historical accuracy.
Stream = low-latency, real-time action.
Over to you: Which do you find harder to scale, batch pipelines or real-time streams?
What are Modular Monoliths?
A modular monolith is an architectural pattern that divides an application into independent modules or components. Each of these modules has well-defined boundaries that group related functionalities. Doing so results in better cohesion.
Here are the main characteristics of modular monoliths:
The modules are independent.
Each module provides a specific functionality.
Each module should expose a well-defined interface.
What is the main advantage of modular monoliths?
A monolith clubs all the functionalities into one big deployment unit. This makes monoliths simple to understand.
Microservices distribute the functionalities into separate deployable units. This makes them more scalable.
However, A modular monolith divides the application into modules that are part of the same deployment unit. They combine the simplicity of traditional monolithic applications with the flexibility of microservices.
In other words, you can have the best of both worlds with modular monoliths.
So - have you used modular monoliths to build applications?
Popular interview question: What is the difference between Process and Thread?
Main differences between process and thread:
Processes are usually independent, while threads exist as process subsets.
Each process has its own memory space. Threads that belong to the same process share the same memory.
A process is a heavyweight operation. It takes more time to create and terminate.
Context switching is more expensive between processes.
Inter-thread communication is faster for threads.
How AI Agents Chain Tools, Memory, and Reasoning?
Reasoning: This is the brain of the AI agent. It receives the user’s goal as a query and uses its reasoning agent (using frameworks like ReAct) to break the goal into a series of smaller, logical steps.
Tools: For each step, the agent selects an appropriate tool. These can be external programs or APIs that it can call upon, such as a web search, a calculator, a code interpreter, or documents.
Memory: This is like the notebook. The agent records the outcome of each tool’s use in its memory. This notebook allows it to learn from results, maintain context over long conversations, and refine its plan based on new findings.
This continuous loop of reasoning, acting with a tool, and remembering the outcomes creates a chain. Finally, when the agent is satisfied that it has fulfilled the user’s query, it responds to the user.
Over to you: Have you used AI agents?
Help us Make ByteByteGo Newsletter Better
TL:DR: Take this 2-minute survey so I can learn more about who you are, what you do, and how I can improve ByteByteGo
SPONSOR US
Get your product in front of more than 1,000,000 tech professionals.
Our newsletter puts your products and services directly in front of an audience that matters - hundreds of thousands of engineering leaders and senior engineers - who have influence over significant tech decisions and big purchases.
Space Fills Up Fast - Reserve Today
Ad spots typically sell out about 4 weeks in advance. To ensure your ad reaches this influential audience, reserve your space now by emailing sponsorship@bytebytego.com.
Great breakdown of Docker vs Kubernetes - that visual really clarifies the architectural difference! Docker is perfect for dev environments and simple deployments, but once you need auto-scaling, self-healing, and multi-host orchestration, K8s becomes essential. On the sponsored content: the AWS + Datadog ebook on cloud architecture diagrams is timely. Documenting cloud architectur is often an afterthought, but proper diagrams are crucial for incident response and onboarding. The batch vs stream processing section was excellent too - in my experience, hybrid architectures (Lambda for real-time enrichment, batch for reprocessing) are becoming the norm. Most teams need both approaches depending on the use case.
Thanks for posting, looking for more conect like that