๐๐๐ฟ๐ฎ๐ฏ๐น๐ฒ ๐ข๐ฟ๐ฐ๐ต๐ฒ๐๐๐ฟ๐ฎ๐๐ถ๐ผ๐ป, a.k.a. ๐ฆ๐๐ฎ๐๐ฒ๐ณ๐๐น ๐๐ ๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐ฎ.๐ฌ.
The closing meetup episode of 2024 is now released.
https://t.co/SWtqHabF1c
https://t.co/J11rnpjqwX
Would be great to build this together in 2025 and beyond!
Just out: The SysDesign Meetup on Stateful Orchestration.
From total order and vector clocks to @temporalio as the mechanism to enable sophisticated distributed design patterns.
Video: https://t.co/EnP8ewEPGu
Slides: https://t.co/AI7Jnsl1fp
Timekeys: https://t.co/T35nkaK0VV
The next โ Educational โ episode of the meetup is up.
Never confuse functional, integration, regression, and end-to-end tests again!
Moreover, don't take this very question seriously. For if you want to set things straight, offense is the best defense!
https://t.co/Vrqj1dqwfd
Publishing Enriched Data Update Events,
"When caching and "poor man's replication" play well together."
I've put together quite a few thoughts, and would appreciate external wisdom at how to approach them from the larger eng org standpoint.
https://t.co/SKZpKHi051
"Benchmarking Production Systems", a new @SysDesignMeetup episode.
There is much more to load testing than just figuring out how many requests can a service handle per second.
Video: https://t.co/m2vD5vrI0B
Slides: https://t.co/FolqrzK9h5
Released the Distributed Task Queue episode.
Thinking of how to schedule and orchestrate tasks from first principles, from the basics, through decoupling task creation from the workers, and all the way to treating the task queue as the source of truth.
https://t.co/D4pz1Wahy8
We are at 1K YouTube subscribers.
Having said anything along the lines of "please subscribe" exactly zero times, this feels like a reasonable milestone to celebrate๐ผ
New meetup episode: Leveraging the Cores.
Coroutines, green threads, and actor models.
We start deep, as usual, from the history of CPUs and OS kernels.
https://t.co/wMdzGk8Lmd
New guest blog post, authored by @UniqueDima (one of our long-standing interviewers). It's about how much communication ability actually matters in technical interviews (spoiler: not as much as you might think).
https://t.co/OmRB5oRoS5
Seriously, why is it "systems design" now?
All my life it was System Design.
And I've never heard of "interiors design", just Interior Design.
Where's the catch?
Following up on the last #Kafka and #RabbitMQ episode, a few short, single digit minutes, cuts from the video.
Intros to both, Kafka consumers & groups, offset tracking, append-only logs written to disk, a bit of Erlang, heartbeats, total & partial order.
https://t.co/2e0f1ozE3Y
Not sure how likely this is to be the best competitive analysis of #Kafka and #RabbitMQ out there.
But it should come very close, especially if you, like me, respect the fundamentals and think from first principles.
https://t.co/eBww7DFGtb
https://t.co/GY06pPG5Bd
Thanks folks!
Why do people call it "systems design" more and more?
It's system design, folks. The design of a system.
Like engine design, or user experience design, or website design. No reason to change the language as of now.