256 Photos and videos
Pinned Tweet
Apr 27
I’ve moved my personal site to rystsov.com
The old domain is no longer under my control, so please update any links if you can 🙏
1
3
483
Denis Rystsov retweeted
23 Nov 2025
Spent some time digging into the #CASPaxos paper ("Replicated State Machines without logs"), by @rystsov. It's really easy to follow; do I get it right though that two competing writers could block each other from ever moving beyond the prepare phase?
arxiv.org/abs/1802.07000
2
7
48
6,091
24 Jul 2025
Well, always has been.. Grep is essential for coding — AI or not
23 Jul 2025
turns out that the backbone of agentic AI coding is grep
1
3
694
26 Sep 2024
Surprising how wrestling with JavaScript years ago helped me onboard with modern C & Seastar (cooperative concurrency within core-pinned threads) to develop Redpanda, a distributed streaming platform
1
501
26 Sep 2024
Now it's paying off again with SwiftUI, which feels a lot like React
1
414
26 Sep 2024
Took me 4 months to get proficient in SwiftUI & iPhone development
1
624
22 Aug 2024
Started iOS programming to build a Strava-like app for surfers and stumbled on a great life hack.
1
1
507
22 Aug 2024
I delayed implementing persistence, which made me repeatedly enter data. This exposed every UX flaw until I couldn't ignore them anymore. A great way to overcome initial blindness to your own errors!
4
380
Denis Rystsov retweeted
7 Aug 2024
One idea for a high perf web framework would be to adopt a native pipes and filters architecture without controllers or concepts like that on top.
Each pipe or filter gets to pre-inspect the req before processing to demand a contiguous memory arena for the response…
4
1
17
2,920
3 Aug 2024
I guess software complexity is often hidden beneath the surface, but with physical objects, you can’t ignore it when it’s right in front of you. This forces management to prioritize it sooner
1
2
5
1,247
Denis Rystsov retweeted
31 Jul 2024
Funemployment means fun blog posts! Please enjoy a categorization of replication algorithms by failure handling strategies; their optimizations, tradeoffs, and complexities; and how this all affects their resource efficiency, latency, and availability.
transactional.blog/blog/2024…
2
52
294
47,907
Denis Rystsov retweeted
8 Jul 2024
Just wrote an article with quick recap of the first @localfirstconf.
Like that “X event in 15 minutes” videos, but in text.
For me, it was the best conference this year and the whole Local-First are is right now the coolest webdev topic.
evilmartians.com/chronicles/…
4
24
4,543
Denis Rystsov retweeted
27 Jun 2023
🚨BREAKING NEWS: #Redpanda has raised $100M in Series C funding, led by @LightspeedVP, @GVteam, and @HaystackVC! Our team is dedicated to enabling #data-intensive apps with new foundational capabilities beyond the scope of legacy #streamingdata platforms.
rpnda.co/46n3P8V
3
16
92
20,613
Denis Rystsov retweeted
17 May 2023
Hey Denise, great article! You might also find this paper interesting: usenix.org/system/files/conf…
They talk about how local file-system faults often lead to global, cluster-wide negative consequences!
2
1
4
1,004
Denis Rystsov retweeted
16 May 2023
If you like working on distributed systems and think through hard and nuanced problems like 👇, join us! redpanda.com/careers
16 May 2023
📢 Just published a blog post discussing the ramifications of running a replicated system without fsync. Contrary to popular belief, the loss of data on a single node can actually result in the loss of replicated data on all nodes. 🔄
redpanda.com/blog/why-fsync-…
2
7
33
10,161
16 May 2023
📢 Just published a blog post discussing the ramifications of running a replicated system without fsync. Contrary to popular belief, the loss of data on a single node can actually result in the loss of replicated data on all nodes. 🔄
redpanda.com/blog/why-fsync-…
6
39
190
65,082
16 May 2023
The argument mentioned above is a misconception. Even the loss of power on a single node, resulting in the local loss of unsynchronized data, can lead to silent global data loss in a replicated system that does not employ fsync, regardless of the replication protocol utilized 😮
2
2
14
2,482
16 May 2023
In my latest blog post, I demonstrate that this is a fundamental finding that applies to all non-Byzantine replication protocols. Furthermore, I provide a compelling example illustrating how data loss on a single node can trigger the loss of data in the whole Kafka cluster.
1
10
3,156