<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://washiul.com/</id><title>Washiul Alam</title><subtitle>A personal blog where I write about building backend systems in the real world. Scalable APIs, distributed systems, databases, infrastructure, and low-level engineering, based on hands-on experience with Java, Go, PostgreSQL, Docker, Linux, and AWS.</subtitle> <updated>2026-01-08T16:54:18+06:00</updated> <author> <name>Washiul Alam Shohan</name> <uri>https://washiul.com/</uri> </author><link rel="self" type="application/atom+xml" href="https://washiul.com/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://washiul.com/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Washiul Alam Shohan </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Implementing WebSockets in Go using Gorilla WebSocket</title><link href="https://washiul.com/posts/go-websockets-part-1/" rel="alternate" type="text/html" title="Implementing WebSockets in Go using Gorilla WebSocket" /><published>2025-12-11T20:39:00+06:00</published> <updated>2025-12-11T20:39:00+06:00</updated> <id>https://washiul.com/posts/go-websockets-part-1/</id> <content type="text/html" src="https://washiul.com/posts/go-websockets-part-1/" /> <author> <name>sohan</name> </author> <category term="Go" /> <category term="WebSocket" /> <summary>If you are building a standard CRUD application, suppose a to-do list, HTTP is all you need. The client asks the server for the data, the server provides it, and the transaction ends. It’s simple, stateless, and easy to scale. But think what the case will be if we were to build a chatting application, the requirements are fundamentally different. When a client sends a message to a room in the ...</summary> </entry> </feed>
