Networking with Go, Made Easy — New Chaptershttps://sazardev.github.io/networking-with-go/feed.xml2026-08-07T18:13:21ZOmar Flores Salazar About the Authorhttps://sazardev.github.io/networking-with-go/read/front-matter/01-about-the-author.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"I don't know your name, your age, or your story. But if you're reading this, you're already on the path — and I'm rooting for you." Introduction to Networkinghttps://sazardev.github.io/networking-with-go/read/networking-foundations/01-introduction-to-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZSomewhere in the last few seconds, before you even opened this book, your phone quietly asked the world a question. Maybe it checked for a new message. Maybe it refreshed a weather forecast, or synced a photo, or pinged a server to see if a… History and Evolution of Computer Networkshttps://sazardev.github.io/networking-with-go/read/networking-foundations/02-history-and-evolution-of-computer-networks.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a world where computers are like islands, isolated and alone, unable to share their treasures. Now, picture bridges being built, one by one, until a vast, bustling metropolis emerges — this is the story of computer networks!" This … Types of Networks: LAN, WAN, MAN, PANhttps://sazardev.github.io/networking-with-go/read/networking-foundations/03-types-of-networks-lan-wan-man-pan.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZRight now, within arm's reach of you, there is very likely a network so small and so intimate that you have never once thought of it as a network at all. If you are listening to anything through wireless earbuds, a burst of radio energy is … Network Topologies and Architectureshttps://sazardev.github.io/networking-with-go/read/networking-foundations/04-network-topologies-and-architectures.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZPicture, for a moment, the street plan of a city you know well. Some cities grew around one great square, with every road eventually leading back to it. Some grew as a grid, endlessly repeatable, block after identical block. Some grew as a … The OSI and TCP/IP Modelshttps://sazardev.github.io/networking-with-go/read/networking-foundations/05-the-osi-and-tcp-ip-models.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZTry, for a moment, to actually hold the whole journey of a single email in your head at once: the words you typed, encoded into bytes; those bytes broken into chunks and numbered so they can be reassembled in order; each chunk wrapped in an… Understanding IP Addressing and Subnettinghttps://sazardev.github.io/networking-with-go/read/networking-foundations/06-understanding-ip-addressing-and-subnetting.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZImagine, for a second, a planet with no postal codes at all — just billions of buildings, no street names, no way to say "the third house past the bakery" to anyone who isn't already standing next to you. Every letter would have to be deliv… Ports, Sockets, and Endpointshttps://sazardev.github.io/networking-with-go/read/networking-foundations/07-ports-sockets-and-endpoints.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZLook at your laptop right now, before you read another word. It is almost certainly not doing one thing on the network — it is doing five or six at once, and you don't feel any of it happening. A mail client is quietly polling for new messa… TCP vs UDP: Concepts and Use Caseshttps://sazardev.github.io/networking-with-go/read/networking-foundations/08-tcp-vs-udp-concepts-and-use-cases.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZSomewhere around 1980, a small group of engineers had to make a decision that every single video call, download, and multiplayer match you've ever used still lives inside of today. IP, the addressing layer underneath everything, had just be… Common Network Protocols (HTTP, FTP, DNS, etc.)https://sazardev.github.io/networking-with-go/read/networking-foundations/09-common-network-protocols-http-ftp-dns-etc.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZImagine two strangers, neither speaking a word of the other's language, trying to complete a business deal through gestures alone. It can be done, badly, with enough patience and luck. Now imagine instead that both of them have quietly agre… Network Security Fundamentalshttps://sazardev.github.io/networking-with-go/read/networking-foundations/10-network-security-fundamentals.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZIn 1971, an experimental little program called Creeper began quietly hopping between mainframes on the ARPANET, displaying a single, oddly cheerful taunt on whatever screen it landed on: "I'm the creeper, catch me if you can!" It didn't ste… Firewalls, NAT, and VPNshttps://sazardev.github.io/networking-with-go/read/networking-foundations/11-firewalls-nat-and-vpns.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine your network as a medieval city: firewalls are the city walls and gates, NAT is the clever gatekeeper who knows everyone's real and fake names, and VPNs are secret tunnels that let you travel safely, unseen by prying eyes!" Picture… Network Troubleshooting and Toolshttps://sazardev.github.io/networking-with-go/read/networking-foundations/12-network-troubleshooting-and-tools.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine you're a digital detective, following clues through tangled wires and invisible signals to solve the mystery of a slow or broken network. With the right tools and a sharp mind, no problem is unsolvable!" On September 9, 1947, an en… Performance, Latency, and Bandwidthhttps://sazardev.github.io/networking-with-go/read/networking-foundations/13-performance-latency-and-bandwidth.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a race car on a track: speed, smooth turns, and pit stops all matter. In networking, performance, latency, and bandwidth are the keys to winning the digital race!" In August 1858, after a fleet of ships had spent weeks laying nearl… Installing Go and Your First Programhttps://sazardev.github.io/networking-with-go/read/go-fundamentals/01-installing-go-and-your-first-program.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery craftsperson remembers the day their first real tool arrived. Not a toy version, not a borrowed one — the actual thing, sitting on the bench, waiting to be plugged in and tried. That's this chapter. Part 1 spent thirteen chapters buil… Variables, Types, and Constantshttps://sazardev.github.io/networking-with-go/read/go-fundamentals/02-variables-types-and-constants.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery program you will ever write, underneath all its cleverness, is just data being stored, read, and transformed — a value coming in from somewhere, sitting in memory for a while, and eventually going somewhere else. That sounds almost to… Functions and Methodshttps://sazardev.github.io/networking-with-go/read/go-fundamentals/03-functions-and-methods.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZThe previous chapter was about data sitting still — a labeled box, holding a value, refusing to change shape. This chapter is about motion: taking that data and doing something to it, in a way you can name, reuse, and trust to behave the sa… Structs and Interfaceshttps://sazardev.github.io/networking-with-go/read/go-fundamentals/04-structs-and-interfaces.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAsk a programmer coming from Java, C++, or Python what they miss most when they first pick up Go, and the honest ones will usually say the same thing: classes. No class keyword, no extends , no inheritance chain to climb when you're trying … io.Reader, io.Writer, and Streaming Datahttps://sazardev.github.io/networking-with-go/read/go-fundamentals/05-io-reader-io-writer-and-streaming-data.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery networked program in Go moves bytes. A TCP connection reads bytes from the network and writes bytes back. An HTTP handler reads a request body and writes a response body. A file server reads a file from disk and writes it to a socket.… Slices, Arrays, and Mapshttps://sazardev.github.io/networking-with-go/read/go-fundamentals/06-slices-arrays-and-maps.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZLook back at every code example in the last chapter and a pattern shows up you probably didn't stop to question: []Rectangle , []T , and — a few chapters from now — things like map[string]int showing up as casually as int or string ever did… Error Handling in Gohttps://sazardev.github.io/networking-with-go/read/go-fundamentals/07-error-handling-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZIf you've written code in almost any other mainstream language, you've lived with try / catch , and probably been bitten by it at least once — an exception thrown three layers deep in a library you didn't write, caught (or not) in a handler… Packages, Modules, and go.modhttps://sazardev.github.io/networking-with-go/read/go-fundamentals/08-packages-modules-and-go-mod.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery program in this book so far has fit comfortably in one file. That won't last, and it shouldn't — a real project needs to split into pieces that different people, or even just a future, more tired version of you, can work on without st… Testing Basics with go testhttps://sazardev.github.io/networking-with-go/read/go-fundamentals/09-testing-basics-with-go-test.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAsk a Go programmer what surprised them most moving from another language, and after "no exceptions" the next answer is often "there's nothing to install to write a test." No framework to choose between, no assertion library to argue about … Goroutines, Channels, and Concurrencyhttps://sazardev.github.io/networking-with-go/read/go-fundamentals/10-goroutines-channels-and-concurrency.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEverything in this part of the book so far has been building toward this one chapter, whether or not it said so out loud. Go wasn't designed by people trying to build a slightly nicer C. It was designed by people who had spent years at Goog… Setting Up Your Go Development Environmenthttps://sazardev.github.io/networking-with-go/read/core-go-networking/01-setting-up-your-go-development-environment.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZIf you completed Go Fundamentals (the section immediately before this one), your Go toolchain is already installed, your editor is configured, and you have written a dozen programs — feel free to skip to Chapter 3. This chapter is a condens… Go Language Basics for Networkinghttps://sazardev.github.io/networking-with-go/read/core-go-networking/02-go-language-basics-for-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZIf you completed Go Fundamentals , you already know variables, structs, functions, slices, maps, goroutines, and channels — skip to Chapter 3. This chapter is a condensed networking-oriented refresher for readers who started directly in Par… Go Networking Packages Overviewhttps://sazardev.github.io/networking-with-go/read/core-go-networking/03-go-networking-packages-overview.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Go's networking packages are like a box of high-tech LEGO bricks—snap them together and you can build anything from a simple chat app to a global-scale web server!" Working with IP, Ports, and Addresses: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/04-working-with-ip-ports-and-addresses-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine the internet as a vast city. Every building (device) has an address (IP), every door (service) has a number (port), and Go is your GPS, map, and keyring—all in one!" TCP in Depth: Protocol Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/05-tcp-in-depth-protocol-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine sending a letter, but you want to make sure it arrives, in order, and without any missing pages. TCP is the postal service that guarantees delivery, order, and reliability—Go gives you the tools to become a master mail carrier!" UDP in Depth: Protocol Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/06-udp-in-depth-protocol-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine sending postcards—fast, simple, and direct. Sometimes they get lost, sometimes they arrive out of order, but they're perfect for quick messages! UDP is the postcard protocol, and Go lets you send and receive them with ease." Error Handling and Debugging: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/07-error-handling-and-debugging-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine you're a detective in the digital world—errors are your clues, and Go gives you the magnifying glass and notebook to solve every mystery!" Concurrency in Networking: Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/08-concurrency-in-networking-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a busy restaurant kitchen: chefs (goroutines) work on different dishes at the same time, waiters (channels) deliver orders and plates, and the manager (main function) keeps everything running smoothly. Welcome to the world of concu… Context and Cancellation: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/09-context-and-cancellation-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine you're in a busy airport. You're waiting for your flight, but you need to be ready to leave at a moment's notice if your gate changes, your flight is canceled, or you get a call from home. In Go, context.Context is your boarding pa… HTTP: Protocol Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/10-http-protocol-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a postal service: you write a letter (request), send it to an address (server), and wait for a reply (response). HTTP is the protocol that defines how these letters are formatted, sent, and received over the internet." Handling JSON and XML over HTTP: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/11-handling-json-and-xml-over-http-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine you're sending a package (data) through the mail (HTTP). JSON and XML are like the forms you fill out to describe what's inside—structured, standardized, and understood by everyone." WebSockets: Real-Time Communication in Gohttps://sazardev.github.io/networking-with-go/read/core-go-networking/12-websockets-real-time-communication-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a phone call instead of sending letters: both sides can talk and listen at any time, instantly. WebSockets turn HTTP from a one-way street into a two-way highway!" Chat Applications: Design, Protocols, and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/13-chat-applications-design-protocols-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine a group conversation where everyone can speak and listen in real time. Chat applications are the classic use case for WebSockets and real-time networking!" File Transfer Applications: Protocols and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/14-file-transfer-applications-protocols-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Sending a chat message is like passing a note across the room. Sending a file is like passing an entire box of documents — you need to say how big the box is, make sure nothing falls out along the way, and confirm the recipient got every l… Proxy Servers and Clients: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/15-proxy-servers-and-clients-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A proxy is like the receptionist at a busy office: visitors don't walk straight to an employee's desk — they talk to the receptionist, who decides who to route them to, checks their badge, and sometimes just answers the question herself fr… DNS: Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/16-dns-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Back in the IP addressing chapter, we compared IP addresses to house addresses. DNS is the phonebook that lets you say 'call the pizza place downtown' instead of memorizing its exact street number. Every time your code dials example.com:44… NAT Traversal and P2P Networking: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/17-nat-traversal-and-p2p-networking-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine two apartment buildings, each with a single front desk that receives all mail for the building. If you want to send a package directly to apartment 4B in the other building, you can't — mail only flows in through the front desk, an… Authentication and Authorization: Security Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/18-authentication-and-authorization-security-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A bouncer at a club does two separate jobs: check your ID to confirm you are who you say you are (authentication), and check the guest list to decide whether that person is allowed into the VIP room (authorization). Mixing up the two jobs … Security in Go Networking: TLS, Encryption, and Best Practiceshttps://sazardev.github.io/networking-with-go/read/core-go-networking/19-security-in-go-networking-tls-encryption-and-best-practices.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Sending data over plain TCP is like shouting across a crowded room — anyone standing between you and the listener can hear every word, and nothing stops them from shouting back pretending to be the person you meant to talk to. TLS is the s… Logging and Monitoring: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/20-logging-and-monitoring-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A server without logging is a black box in flight with no flight recorder: if something goes wrong at 3 a.m., you're left guessing what happened from the wreckage. Logging and monitoring are the instruments on the dashboard — they tell you… Testing and Debugging Go Network Applications: Theory and Practicehttps://sazardev.github.io/networking-with-go/read/core-go-networking/21-testing-and-debugging-go-network-applications-theory-and-practice.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Pilots don't learn to handle engine failure by waiting for one at 30,000 feet — they train in a simulator first. Testing network code is the same idea: you want to exercise timeouts, dropped connections, and concurrent clients on your own … Performance Optimization: Concepts and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/22-performance-optimization-concepts-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Tuning a race car before you've measured its lap times is just guessing with extra steps. Performance work on a network service follows the same rule: profile first, find the actual bottleneck, then change one thing at a time — otherwise y… Deploying Go Network Applications: Best Practiceshttps://sazardev.github.io/networking-with-go/read/core-go-networking/23-deploying-go-network-applications-best-practices.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Building a boat in the workshop and sailing it across open water are two very different challenges. Everything you've built in this part of the book — servers, proxies, clients — has been tested at the dock. Deployment is what happens when… Real-World Projects and Case Studieshttps://sazardev.github.io/networking-with-go/read/core-go-networking/24-real-world-projects-and-case-studies.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"An architect who has only ever looked at blueprints eventually needs to walk through a finished building. This chapter is that walkthrough: stepping back from individual techniques to see how the pieces built across Part 2 combine into the… Email Protocols: Theory and Go Implementationhttps://sazardev.github.io/networking-with-go/read/core-go-networking/25-email-protocols-theory-and-go-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Back in the DNS chapter, net.LookupMX("example.com") returned the mail servers responsible for a domain, and the chapter moved on without explaining what those servers actually do with a message once it arrives. This is that explanation — … Further Resources and Next Stepshttps://sazardev.github.io/networking-with-go/read/core-go-networking/26-further-resources-and-next-steps.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Reaching the end of a map doesn't mean the territory stops — it means it's time for a new map. Part 2 has covered a lot of ground; this chapter looks back at the route, then points at what's next." gRPC and Protocol Buffers in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/01-grpc-and-protocol-buffers-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Imagine two restaurants exchanging orders. One scribbles freeform notes on napkins and hopes the kitchen can guess what "the usual, but spicy" means. The other uses a printed order form with numbered fields: dish ID, quantity, spice level,… WebRTC and P2P Communication in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/02-webrtc-and-p2p-communication-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Two people want to talk directly, but neither knows the other's address. So they both call a mutual friend first, who introduces them and passes along contact details, then steps out of the conversation entirely. From that point on, the tw… MQTT, AMQP, and IoT Messaging Protocolshttps://sazardev.github.io/networking-with-go/read/advanced-specialized/03-mqtt-amqp-and-iot-messaging-protocols.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A radio station does not know or care who is listening. It just broadcasts on a frequency, and anyone with a receiver tuned to that frequency hears it. Compare that to a post office, which needs a specific address, sorts mail into specific… SDN (Software Defined Networking) and OpenFlow with Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/04-sdn-software-defined-networking-and-openflow-with-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A city where every traffic light decides on its own, with no coordination, when to turn green is a city with a lot of avoidable gridlock. A city with one control center watching every intersection and adjusting all the lights together can … Network Function Virtualization (NFV) in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/05-network-function-virtualization-nfv-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A commercial kitchen used to need a dedicated machine for every task: a bread slicer, a meat grinder, a dough mixer, each bolted to the counter, each only able to do its one job. Replace them with a single programmable robot arm that can p… Deep Packet Inspection and Packet Manipulationhttps://sazardev.github.io/networking-with-go/read/advanced-specialized/06-deep-packet-inspection-and-packet-manipulation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A postal sorting facility usually just reads the address on the envelope and routes it accordingly -- it never opens the letter inside. Deep packet inspection is what happens when the sorting facility starts opening every envelope, reading… Custom Protocol Design and Implementationhttps://sazardev.github.io/networking-with-go/read/advanced-specialized/07-custom-protocol-design-and-implementation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Two people inventing a board game together need to agree on more than the pieces. Whose turn goes first? How do you signal that your turn is over? What happens if someone disconnects mid-game? What counts as a valid move, and what happens … Cloud Networking APIs and Automation with Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/08-cloud-networking-apis-and-automation-with-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"There was a time when getting a new network segment meant an order form, a rack visit, someone physically running cable, and a wait measured in weeks. Cloud networking turned that into a vending machine: describe what you want in a request… Zero Trust Networking and Microsegmentationhttps://sazardev.github.io/networking-with-go/read/advanced-specialized/09-zero-trust-networking-and-microsegmentation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"An old-style office building checks your badge at the front door and, once you are inside, lets you walk into any room you like -- the assumption is that anyone who made it past the lobby belongs there. A modern secure facility checks your… Network Simulation and Virtual Labshttps://sazardev.github.io/networking-with-go/read/advanced-specialized/10-network-simulation-and-virtual-labs.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A flight simulator lets a pilot practice an engine failure at ten thousand feet without ever risking a real aircraft or a real passenger. A network simulator offers the same deal to network engineers and protocol developers: try the failur… Automating Network Device Configurationhttps://sazardev.github.io/networking-with-go/read/advanced-specialized/11-automating-network-device-configuration.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A medieval scribe copied books by hand, one letter at a time, and every copy risked a new typo. The printing press didn't just make copying faster — it made every copy identical. Automating network configuration is your printing press: ins… Observability and Tracing in Go Networkinghttps://sazardev.github.io/networking-with-go/read/advanced-specialized/12-observability-and-tracing-in-go-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A pilot doesn't fly by feel — the cockpit is covered in instruments telling her altitude, speed, and fuel before anything goes wrong. A production network service without observability is a pilot flying blind: it might be fine, or it might… Wireless Networking and Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/13-wireless-networking-and-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A wired connection is a conversation through a pipe — say something at one end, it arrives at the other. Wireless is shouting across a crowded room and hoping the right person hears you over everyone else shouting too. The physics are mess… Mesh Networks and Dynamic Routinghttps://sazardev.github.io/networking-with-go/read/advanced-specialized/14-mesh-networks-and-dynamic-routing.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A hub-and-spoke airport is elegant until the hub closes for weather — then every flight is grounded. A mesh is more like a bucket brigade at a fire: nobody carries the water the whole way, but everybody passes it along, and the line rerout… High Availability and Load Balancinghttps://sazardev.github.io/networking-with-go/read/advanced-specialized/15-high-availability-and-load-balancing.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A concert with one entrance is a bottleneck and a fire hazard. A good venue has several doors, staff redirecting people to whichever line is shortest, and a plan for what happens if one door jams. High availability is the plan for the jamm… Real-Time Networking for Gameshttps://sazardev.github.io/networking-with-go/read/advanced-specialized/16-real-time-networking-for-games.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"TCP is a certified letter: guaranteed delivery, guaranteed order, and a receipt to prove it. A multiplayer game needs a walkie-talkie instead — say the player's position now , and if this update gets lost, don't bother resending it, becaus… Blockchain and Cryptocurrency Networkinghttps://sazardev.github.io/networking-with-go/read/advanced-specialized/17-blockchain-and-cryptocurrency-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Picture a room full of strangers who don't trust each other, but who all agree to keep an identical copy of the same notebook. Whenever someone writes a new entry, everyone else checks it, copies it into their own notebook, and tells their… Big Data, AI, and Streaming Networkshttps://sazardev.github.io/networking-with-go/read/advanced-specialized/18-big-data-ai-and-streaming-networks.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"An airport baggage system doesn't wait for every suitcase from every flight to arrive before starting to sort — it's a continuous flow of belts, scanners, and diverters, built to keep moving even when one flight dumps ten times the usual l… Go Networking Performance Benchmarkshttps://sazardev.github.io/networking-with-go/read/advanced-specialized/19-go-networking-performance-benchmarks.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A car might look fast in the driveway. The only way to know for sure is a stopwatch and a track. Benchmarking network code is exactly that: replacing 'this feels quick' with a number you can compare, reproduce, and defend." QUIC and HTTP/3 in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/20-quic-and-http-3-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Every earlier chapter in this book built on the same assumption: sockets are either the ordered, reliable stream of TCP or the fire-and-forget datagrams of UDP, and never both. QUIC breaks that assumption on purpose — it reimplements every… Message Queues and Service Discovery in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/21-message-queues-and-service-discovery-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"The chat server case study mentioned a message bus standing in for an in-process channel once a single process can no longer hold every connection. This chapter is that message bus, made concrete — plus the other half of running many small… IPv6 Networking in Gohttps://sazardev.github.io/networking-with-go/read/advanced-specialized/22-ipv6-networking-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"The IP addressing chapter back in Part 1 explained why IPv6 exists — 340 undecillion addresses instead of 4 billion. Every Go example since then quietly worked whether you gave it an IPv4 or IPv6 address, because the net package was built … Introduction to Cybersecurity in Networkinghttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/01-introduction-to-cybersecurity-in-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A network engineer builds roads between cities. A security engineer asks: who's allowed to drive on them, what happens if a truck crashes in the tunnel, and what do we do if someone forges a license plate?" Threat Modeling and Attack Surfaceshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/02-threat-modeling-and-attack-surfaces.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Before a locksmith recommends a single lock, they walk the whole building: every door, every window, every vent big enough for a cat. Threat modeling is that walk-through, done for software." Common Network Attacks (DoS, MITM, Spoofing, etc.)https://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/03-common-network-attacks-dos-mitm-spoofing-etc.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A pickpocket, a con artist, and a mob blocking the door all want different things, but they all exploit the same crowded street. Network attacks are no different — the wire is the crowded street." Network Scanning and Enumeration with Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/04-network-scanning-and-enumeration-with-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Before a home inspector signs off on a house, they check every door, every window, and every outlet. Network scanning is that inspection, run against a machine instead of a building." Packet Sniffing and Analysis with Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/05-packet-sniffing-and-analysis-with-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A phone tap doesn't change the call — it just listens to a copy of it. Packet sniffing is the network equivalent: a quiet copy of every frame that crosses an interface, for whoever is allowed to look." Vulnerability Assessment and Exploitation Basicshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/06-vulnerability-assessment-and-exploitation-basics.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Finding a crack in the wall is one skill. Judging whether that crack will bring the wall down is another. Vulnerability assessment is the second skill — and it's the one that decides what actually gets fixed first." Building Simple Security Tools in Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/07-building-simple-security-tools-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A carpenter doesn't buy a hammer for every job — sometimes the fastest fix is the one you make yourself, sized exactly to the problem in front of you." Penetration Testing Workflowshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/08-penetration-testing-workflows.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A fire drill isn't useful because you hope for a fire — it's useful because it proves the exits actually work. A penetration test is a fire drill for your network, run by someone trying, on purpose and with permission, to find the exit tha… Incident Response and Forensicshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/09-incident-response-and-forensics.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A pentest asks 'can someone get in?' beforehand. Incident response asks 'someone got in — now what?' afterward. Both matter, but only one of them happens on the worst day of your week." Ethical Hacking and Legal Considerationshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/10-ethical-hacking-and-legal-considerations.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A locksmith who can open any door isn't a criminal — until they open a door that isn't theirs to open, or that no one asked them to. The lockpick is identical either way. Only the permission changes what it means." Implementing TLS/SSL in Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/11-implementing-tls-ssl-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Every letter you've sent so far in this book traveled in a clear envelope anyone along the route could open and read. TLS is the sealed, tamper-evident envelope — and Go makes using one almost as easy as not bothering." Certificate Management and PKIhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/12-certificate-management-and-pki.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"TLS promises the lock on the door is real. A certificate is the notarized paperwork proving the locksmith who installed it is who they claim to be. PKI is the whole system of notaries that makes that paperwork worth trusting." Secure Coding Practices in Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/13-secure-coding-practices-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Most break-ins in a building happen through a door that was left unlocked, not a wall someone tunneled through. Most exploited software bugs are the same: an ordinary mistake, not an exotic attack." Zero Trust Networking Conceptshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/14-zero-trust-networking-concepts.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"The old model of network security was a castle: thick walls, one gate, and anyone inside the walls was assumed friendly. Zero trust assumes the castle has already been infiltrated, and checks everyone's badge at every single door, every si… Network Segmentation and Microsegmentationhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/15-network-segmentation-and-microsegmentation.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A ship isn't built as one open hull — it's divided into watertight compartments, so a single puncture floods one section instead of sinking the whole vessel. Network segmentation is the same idea, applied to compromise instead of seawater.… IDS/IPS: Concepts and Go Implementationshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/16-ids-ips-concepts-and-go-implementations.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"A burglar alarm only tells you a window broke. A guard who slams the door shut before the intruder gets inside is a different job entirely. Intrusion Detection Systems watch and report; Intrusion Prevention Systems watch and act. Most real… SIEM and Log Analysis for Network Securityhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/17-siem-and-log-analysis-for-network-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA single firewall log tells you one connection was blocked. A single server log tells you one login succeeded. Neither tells you a breach happened. Put both in the same room, correlate them by time and identity, and the story suddenly write… Malware Analysis and Network Indicatorshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/18-malware-analysis-and-network-indicators.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZMalware, like a biological pathogen, has to communicate to do damage at scale - it phones home for instructions, exfiltrates what it steals, or spreads to the next host. That communication has to cross the network, and the network is where … Reverse Engineering Network Protocolshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/19-reverse-engineering-network-protocols.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZImagine dropping into a foreign city with no dictionary, only a notebook. You can't read the signs, but you can watch what people do after each exchange - which words make the shopkeeper smile, which make the guard tense up. Given enough co… Red Team vs Blue Team: Concepts and Labshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/20-red-team-vs-blue-team-concepts-and-labs.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChess players get stronger by playing against opponents who actually try to beat them, not by studying the rulebook alone. Security teams are no different: a network defended only on paper, never tested by someone actively trying to break i… Social Engineering in Networkinghttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/21-social-engineering-in-networking.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZYou can harden every firewall rule, patch every server, and encrypt every packet, and an attacker can still walk through the front door simply by asking politely and sounding like they belong. The strongest technical controls in this book a… Wireless Network Security: Theory and Attackshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/22-wireless-network-security-theory-and-attacks.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZWired traffic stays inside a cable; someone has to physically tap it to listen in. Wireless traffic is broadcast into the air for anyone with an antenna and no scruples to receive - the network equivalent of holding a conversation by shouti… IoT Security: Concepts and Go Implementationshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/23-iot-security-concepts-and-go-implementations.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZGive an intern full access to the building and no supervision, and you'd call it a management failure. Yet that's exactly how most IoT devices operate: network access, default credentials nobody rotates, firmware that rarely gets patched, a… Cloud Networking Securityhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/24-cloud-networking-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZRenting an apartment in a large building means the landlord secures the front doors, the elevators, and the foundation, but you're still the one who has to lock your own apartment door and not tape the spare key under the doormat. Cloud sec… Container and Kubernetes Network Securityhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/25-container-and-kubernetes-network-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZContainers are like apartments sharing one building's plumbing and electrical system: each unit feels self-contained, but a serious enough problem in the shared infrastructure below can affect every tenant at once. Understanding exactly whe… Bug Bounty and Responsible Disclosurehttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/26-bug-bounty-and-responsible-disclosure.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZFinding an unlocked door on someone's building puts you in an interesting position: you can walk away, you can shout about it from the rooftop, or you can knock and let the owner know before anyone with worse intentions finds it first. Resp… Security Automation with Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/27-security-automation-with-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA single analyst can carefully review one alert at a time, forever, or a script can watch every alert continuously and only interrupt a human when something actually needs a human. Security automation is not about replacing judgment - it's … Building a Custom Honeypot in Gohttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/28-building-a-custom-honeypot-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA honeypot is a fake vault sitting next to the real one, wired with an alarm and a camera. Nobody with legitimate business ever has a reason to open it, so any interaction with it - by definition - is worth investigating. That single proper… Simulating Attacks and Defense in Lab Environmentshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/29-simulating-attacks-and-defense-in-lab-environments.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA flight simulator doesn't just train pilots on the easy days - it deliberately throws engine failures and storms at them, over and over, in an environment where a mistake costs nothing but a restart. Security skills need the same kind of p… Case Studies: Real-World Network Breacheshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/30-case-studies-real-world-network-breaches.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery concept in this part of the book - segmentation, IDS/IPS, patching discipline, least privilege, social engineering awareness - exists because a real organization, at some point, learned its absence the hard way. Studying how well-docu… Emerging Threats and Future Trends in Network Securityhttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/31-emerging-threats-and-future-trends-in-network-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery technique in this book represents the current state of an arms race that never actually ends - each generation of defenses reshapes what the next generation of attacks has to look like, and vice versa. This closing chapter looks at wh… Further Cybersecurity Resourceshttps://sazardev.github.io/networking-with-go/read/cybersecurity-ethical-hacking/32-further-cybersecurity-resources.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Thirty-one chapters is enough to learn to read a map. It's not enough to know every road. Here's where to keep exploring, both alongside the rest of this book and long after you've finished it." API Fundamentals: REST, HTTP, and the Webhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/01-api-fundamentals-rest-http-and-the-web.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZWelcome to Part APIs . This section builds production-ready HTTP APIs and backends in Go — from net/http fundamentals through frameworks, databases, Docker, cloud deployment, and production architecture. Every chapter pairs concepts with wo… Designing Clean URLs, Query Params, and Routinghttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/02-designing-clean-urls-query-params-and-routing.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZWelcome to the art of designing clean and intuitive URLs. Think of URLs as the street addresses of the web: they guide users and programs to the right destination. A URL is also part of your public API contract — once clients start calling … JSON, XML, and Data Serializationhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/03-json-xml-and-data-serialization.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery API eventually boils down to one question: how do we turn a Go struct into bytes on the wire, and back again? That process is serialization, and Go's standard library gives you two solid, built-in answers — encoding/json and encoding/… Building RESTful APIs with net/httphttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/04-building-restful-apis-with-net-http.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZGo's standard library is unusually capable for building production APIs without a framework. This chapter puts everything from the previous two chapters together — clean routing, query parameters, JSON serialization — into a complete, worki… Building APIs with Ginhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/05-building-apis-with-gin.html2026-08-07T18:13:21Z2026-08-07T18:13:21Znet/http gets you far, but as an API grows — dozens of routes, shared middleware, request binding and validation on every endpoint — the boilerplate adds up. Gin ( github.com/gin-gonic/gin ) is the most widely used Go web framework, built a… Building APIs with Fiberhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/06-building-apis-with-fiber.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZFiber ( github.com/gofiber/fiber/v2 ) is a Go web framework inspired by Express.js, built on top of fasthttp rather than the standard library's net/http . That choice trades some ecosystem compatibility (middleware built for net/http doesn'… Serving HTML, Templates, and Static Fileshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/07-serving-html-templates-and-static-files.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZNot every Go server is a pure JSON API. Sometimes you need to render an actual web page — a dashboard, an admin panel, an email preview — and serve the CSS, images, and JavaScript that go with it. Go's standard library covers both jobs: htm… Adding WebSockets to Your APIhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/08-adding-websockets-to-your-api.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZREST is built around request-response: the client always speaks first. Some features — chat, live dashboards, multiplayer state, collaborative editing — need the server to push data the moment it happens, in both directions, over one long-l… Notifications, SSE, and Real-Time Updateshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/09-notifications-sse-and-real-time-updates.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZNot every real-time feature needs a full duplex WebSocket connection. Notification feeds, live scoreboards, progress bars, and status updates are all one-directional: the server pushes, the client just listens. Server-Sent Events (SSE) solv… API Security: Tokens, Auth, and Best Practiceshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/10-api-security-tokens-auth-and-best-practices.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAn API without authentication is an API anyone can call — including people you didn't intend to let in. This chapter covers the common authentication schemes you'll actually implement, a working JWT setup using golang-jwt/jwt/v5 , password … Rate Limiting, CORS, and API Gatewayshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/11-rate-limiting-cors-and-api-gateways.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAuthentication answers who can call your API. This chapter covers three separate but related concerns that shape how much they can call it, from where, and — as your API grows — whether a dedicated layer in front of it should handle all of … API Documentation and OpenAPI/Swaggerhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/12-api-documentation-and-openapi-swagger.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA REST endpoint is only as useful as its documentation. OpenAPI (formerly known as Swagger) is the industry-standard, machine-readable format for describing an HTTP API — its paths, request/response shapes, authentication, and error codes —… Testing and Mocking APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/13-testing-and-mocking-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAn API without tests is a promise you can't verify. Go's standard library makes HTTP handler testing unusually pleasant: net/http/httptest lets you exercise a handler directly, in-process, without binding a real port or making a real networ… Versioning, Deprecation, and Maintenancehttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/14-versioning-deprecation-and-maintenance.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZOnce an API has real clients, it can't just change shape overnight — every field renamed or endpoint removed is a broken integration somewhere. Versioning is how you evolve an API without breaking the clients depending on its current behavi… Prebuilt Solutions and API Boilerplateshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/15-prebuilt-solutions-and-api-boilerplates.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery chapter so far has built things from small pieces — a mux, a middleware chain, a JWT check — on purpose, so the mechanics are visible. In real projects, you don't always want to start from an empty main.go . This chapter surveys the G… API Performance, Monitoring, and Observabilityhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/16-api-performance-monitoring-and-observability.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAn API running in production without visibility into its own behavior is a black box — you find out something's wrong when a user complains, not when it starts happening. Observability covers three complementary signals: structured logs (wh… Deploying and Scaling Go APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/17-deploying-and-scaling-go-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEverything up to this point has run on a developer's laptop. This chapter covers what changes when a Go API needs to run reliably, at scale, in production: building deployable artifacts, containerizing them, running multiple instances safel… Advanced API Rate Limiting and Anti-Abusehttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/18-advanced-api-rate-limiting-and-anti-abuse.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZThe rate limiting in an earlier chapter used an in-memory rate.Limiter per client — good enough for a single instance, but it breaks down the moment you run more than one, since each instance tracks its own limits independently. This chapte… Advanced API Gateway and Service Meshhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/19-advanced-api-gateway-and-service-mesh.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZOnce an API stops being "one server answering requests" and becomes a dozen services calling each other, two new problems show up. First, clients need a single, stable front door instead of having to know about every internal service. Secon… APIs for Graph Databases and NoSQLhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/20-apis-for-graph-databases-and-nosql.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZNot every API sits in front of a relational database. Once your data looks like a network of relationships (who follows whom, which products were bought together), or like loosely structured documents (user profiles with optional fields, ev… APIs for Background Jobs and Task Queueshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/21-apis-for-background-jobs-and-task-queues.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZSome work is too slow to do inside an HTTP request. Sending a confirmation email, generating a PDF invoice, resizing an uploaded image, or calling a flaky third-party API can take anywhere from a second to several minutes — far longer than … APIs for File Uploads, Media, and Streaminghttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/22-apis-for-file-uploads-media-and-streaming.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZJSON payloads are small and fit comfortably in memory. Files don't. A profile picture is a few hundred kilobytes; a video upload can be gigabytes. An API that treats every request body the same way — read it all into memory, then process it… APIs for Webhooks and Event-Driven Designhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/23-apis-for-webhooks-and-event-driven-design.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZMost of this book so far has been about APIs where the client asks and the server answers. A webhook flips that around: the server calls the client, unprompted, when something happens. Stripe tells your server a payment succeeded; GitHub te… APIs for OAuth2, SSO, SAML, OpenID Connecthttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/24-apis-for-oauth2-sso-saml-openid-connect.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z"Sign in with Google" buttons, corporate single sign-on portals, and API access tokens all rest on a small set of standards that are frequently confused with each other. OAuth2 is an authorization framework — it lets a user grant a third-pa… APIs for Multi-Tenancy and SaaShttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/25-apis-for-multi-tenancy-and-saas.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA multi-tenant API serves many independent customers ("tenants") from the same running application and, usually, the same database — a project management tool where Acme Corp and Globex Inc both use the product without ever seeing each othe… APIs for Internationalization (i18n) and Localization (l10n)https://sazardev.github.io/networking-with-go/read/production-apis-architecture/26-apis-for-internationalization-i18n-and-localization-l10n.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZInternationalization (i18n — eighteen letters between the "i" and the "n") is the work of designing your API so it can support multiple languages, currencies, and regional formats. Localization (l10n) is actually producing that content for … APIs for Feature Flags and Dynamic Confighttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/27-apis-for-feature-flags-and-dynamic-config.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery deploy used to mean "this code is now live for everyone." Feature flags decouple those two things: the code can be deployed dark, and turned on for 1% of users, then 50%, then everyone — or turned back off instantly if something looks… APIs for Load and Stress Testinghttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/28-apis-for-load-and-stress-testing.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZUnit tests tell you your API behaves correctly for one request at a time. They tell you nothing about what happens when a thousand requests arrive per second, or what breaks first when traffic keeps climbing past what you tested. Load testi… APIs for CI/CD and DevOpshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/29-apis-for-ci-cd-and-devops.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZContinuous integration and deployment pipelines are themselves driven by APIs — GitHub Actions, GitLab CI, and every cloud provider's deployment service expose an HTTP API underneath their UI, and your Go services frequently need to talk to… APIs for Serverless and FaaShttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/30-apis-for-serverless-and-faas.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEverything so far in this book has assumed a long-running process: a Go binary that starts, listens on a port, and handles requests until it's stopped. Function-as-a-Service (FaaS) platforms — AWS Lambda, Google Cloud Functions, Azure Funct… APIs for Edge Computing and CDNhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/31-apis-for-edge-computing-and-cdn.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZA traditional API runs in one region (or a handful) and every client, no matter where they are in the world, pays the network latency of reaching it. Edge computing flips that: your code runs in dozens or hundreds of points of presence spre… APIs for Advanced Securityhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/32-apis-for-advanced-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZBasic API security — hashing passwords, checking a bearer token — gets you through the first year of a project. This chapter covers what shows up once an API has real operational maturity behind it: rotating signing keys without breaking al… APIs for Advanced Observability: Metrics and Logginghttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/33-apis-for-advanced-observability-metrics-and-logging.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZAn earlier chapter in this book covered basic performance monitoring — enough to notice that something is slow. This chapter is about instrumenting an API properly: structured logs you can actually query, metrics that answer specific operat… APIs for Advanced Observability: Distributed Tracinghttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/34-apis-for-advanced-observability-distributed-tracing.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZThe previous chapter instrumented a single service well: structured logs, metrics, health checks. But a request to a modern API rarely stays inside one service — it hits a gateway, calls three internal services, one of which queries a datab… RPC and gRPC for APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/35-rpc-and-grpc-for-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZSo far, almost every API in this part of the book has spoken the same dialect: resources, HTTP verbs, and JSON. That dialect is REST, and it earns its popularity because a browser, a curl command, and a stranger's Postman collection can all… Working with SQL Databases: PostgreSQLhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/36-working-with-sql-databases-postgresql.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery API in this book so far has kept its data in memory or behind an external service. Real APIs need real, durable storage, and for most backend services that means a relational database. PostgreSQL is the default choice for a huge share… Working with SQLite in Gohttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/37-working-with-sqlite-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZThe previous chapter treated PostgreSQL as the default choice for a Go API's storage. It is a good default, but it is not the only reasonable one. SQLite -- an entire relational database engine compiled into a single library, with no separa… Containerizing Go APIs with Dockerhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/38-containerizing-go-apis-with-docker.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery API built so far in this book runs however you happen to launch it: go run main.go on your laptop, or a binary copied onto a server by hand. That works until you need the exact same artifact to run identically on a teammate's machine,… Clean Architecture for Go APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/39-clean-architecture-for-go-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery chapter so far has built one slice of an API — routing, auth, rate limiting, observability. This chapter and the three that follow it step back and ask a different question: once you have all those slices, how do you arrange them so t… Hexagonal Architecture (Ports and Adapters) for Go APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/40-hexagonal-architecture-ports-and-adapters-for-go-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChapter 6.39 drew Clean Architecture as concentric rings and established the rule that matters: dependencies point inward, and domain logic never imports a framework or a driver. Alistair Cockburn's Hexagonal Architecture — also called Port… Domain-Driven Design in Gohttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/41-domain-driven-design-in-go.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChapters 6.39 and 6.40 answered "which package can import which." This chapter answers a different question: once your domain logic lives in its own package, protected from frameworks and databases, how do you design the types inside that p… Building a Complete Project End-to-Endhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/42-building-a-complete-project-end-to-end.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZThe last three chapters built the order-management example in pieces: the package layout and dependency direction (Chapter 6.39), the ports-and-adapters vocabulary and a fast in-memory test double (Chapter 6.40), and the DDD-modeled Order a… Deploying to Google Cloudhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/43-deploying-to-google-cloud.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChapter 6.38 covered building a Go API into a small, distroless container image with a multi-stage Dockerfile, and Chapter 6.17 covered the general shape of running that image reliably at scale. This chapter takes that same image and deploy… Orchestration, Replicas, and Graceful Shutdownhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/44-orchestration-replicas-and-graceful-shutdown.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChapter 6.17 introduced running multiple replicas behind a load balancer and sketched a first graceful shutdown using signal.NotifyContext and http.Server.Shutdown . This chapter goes deeper on both halves of that picture: exactly what runn… Thinking Like an Attacker: API Securityhttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/45-thinking-like-an-attacker-api-security.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZChapter 6.10 built authentication and Chapter 6.11 added rate limiting at the traffic level — both defensive, both essential, and both easy to trust a little too much on their own. A valid token or a request under the rate limit only proves… Caching and Redis for Go APIshttps://sazardev.github.io/networking-with-go/read/production-apis-architecture/46-caching-and-redis-for-go-apis.html2026-08-07T18:13:21Z2026-08-07T18:13:21ZEvery database chapter so far assumed each request earns its own round trip to PostgreSQL or SQLite. For a lot of endpoints that's perfectly fine—but some queries get asked thousands of times a minute for data that barely changes: a product… A Final Wordhttps://sazardev.github.io/networking-with-go/read/back-matter/01-a-final-word.html2026-08-07T18:13:21Z2026-08-07T18:13:21Z