avrl ☘
@avrldotdev • 9,779 subscribers
Backend Dev | Open Source Contributor | Medium: https://t.co/mtXbyXM0As
Videos
Day 1 of learning Go after office hours. Built a simple HTTP server (with routes) & learnt basic semantics with pointers, interfaces & structs This project will finally turn into implementation for Raft from the official paper (link in comments) Go is pretty nifty & cool :)
avrl ☘283,161 views • 4 months ago
Day 3 of learning Go after office hours Studied about Concurrency in Go: - how Go handles concurrency - Locks and Mutex - Goroutines - Channels (sender & receiver pattern) It's very intuitive in Go coming from some experience in Java. Will deep dive more in the coming days!
avrl ☘82,127 views • 4 months ago
Day 2 of learning Go after office hours More progress on HTTP server (with routes). This HTTP server will finally act as a gateway service that will serve client requests by calling the Raft Cluster (leader) deployed separately. Next stop: Goroutines, channels & concurrency
avrl ☘79,076 views • 4 months ago
Day 4 learning Go after office hours (Weekend) Gateway server is now ready & complete! - dived deeper into Go's concurrency - learnt several mutex & channel patterns - read about Go runtime internals & GC Next up: Raft Implementation Sharing the design & some write-ups soon!
avrl ☘21,490 views • 4 months ago
Day 6 of learning Go after office hours Carved out an impl plan for the core logic. Did 1 hour QnA with GPT 5.5 & got grilled hard (it was fun) The Gateway now sends requests to my internal leader node & internal scaffolding is done! Onto core logic implementation for Raft!
avrl ☘18,296 views • 3 months ago
Day 5 of learning Go after office hours. Started with implementing Raft algo & project design is: N number of nodes (Go servers) inside a K8s StatefulSet with a gateway service deployed separately routing requests from the clients to the leader of that cluster. Gateway service can ping the current leader but if it changed, the node will respond with the new leaders address & the service will send a new req to the new leader. (You can loosely say its acting like a reverse proxy. We can also route the req from the follower internally to the new leader but I want to keep that limited to Gateway) Each node will have its own persistence (sql DB) & a log file (for recording ops from client). It's a fairly simple setup & I aim to learn some DevOps too with it projects on orchestration & deployments. (Design diagram in comments)
avrl ☘15,360 views • 3 months ago
No more content to load