Channel
@drim_system_design_channel
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Handles named that no longer answer · Cite this entry
232subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001403138685 |
|---|---|
| Type | Channel |
| Username | @drim_system_design_channel |
| Created | Between 1 December 2018 and 6 April 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/drim_system_design_channel |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 14:41 | 232 | -1 |
| 8 Sept 2026, 15:22 | 233 | no change |
| 30 Aug 2026, 03:13 | 233 | -1 |
| 7 Aug 2026, 14:36 | 234 | first reading |
20 posts held, back to 6 April 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 December 2024. An engagement rate over an empty window would be a number about nothing.
46 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 45.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 21 | 45.7% | |
| 👍 | 20 | 43.5% | |
| ❤ | 3 | 6.52% | |
| 💯 | 1 | 2.17% | |
| 🙏 | 1 | 2.17% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 April 2021 to 12 December 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
From this comparison, it is clear that Hetzner provides the cheapest virtual machines. However, the significant disadvantage of Hetzner until recently was the lack of S3-compatible object storage. The S3 API is the de facto standard in the industry. Many applications use it to store data. Finally, the situation has changed, and Hetzner launched such storage a week ago. Now, we can run many more system types using th…
🔥6❤1👍1
What cloud providers do you use? Multiple answers possible.
The shares total 138%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Let's step away from the Uber discussion for a moment. Today, I want to discuss a common task. Suppose you are developing a system and want to launch it in the cloud. Many different cloud providers exist, and you have to select one. Numerous factors influence the decision-making process, and pricing is among the most important. Let's compare the prices of virtual machines offered by some popular providers. We'll use …
🔥6👍1
API Gateway In the previous post, we discussed the Uber microservices architecture. The transition from monolith to microservices had its pros and cons. One drawback was the increased complexity. For example, the way clients access the system API has changed. Previously, there was a single monolith process for receiving all requests. Clients used a DNS name and a specific port to connect to that process. However, af…
👍11🔥2💯1
I am resuming publication on the channel after a break due to personal reasons. Thank you for staying on the channel! ☀️
🔥7👍1
Microservices During its early years, Uber focused on delivering essential features and rapid growth. This is why the team used a monolithic architecture with a single PostgreSQL instance. Like most successful startups, they wanted to keep things simple until the business model was validated. The problems arose a few years later when the monolith grew big. I think many of you have worked with monolithic application…
👍4❤2
Uber In the next few posts, I will use Uber as a showcase to cover several fundamental software architecture topics. Uber is a ride-sharing application based on a single idea "What if you could request a ride from your phone?" Two friends, Travis Kalanick and Garrett Camp launched it in San Francisco in 2010. Ten years later, it operated in over 10,000 cities globally. This explosive growth has presented many chal…
👍2
Need motivation to learn systems design? Read this post. The author describes how he spent six months preparing for interviews at top tech companies. As a result, he received an offer with a total compensation of 593 thousand dollars (nearly 50 thousand dollars per month). The author gives specific advice on what to study and at what depth. Interestingly enough, he mentions several topics that we've already discusse…
Numbers Everyone Should Know We are software engineers. Like other engineers, we need to know the fundamental principles of the systems we deal with. For example, mechanical engineers understand the strength numbers of aluminum and titanium and, accordingly, which metal to use in which case. Do you know the performance numbers of modern computer systems? Here are some of them: Operation | Latency ----…
B-tree vs. LSM-tree Imagine there is a database with customer records, and we want to find a customer with id equal 52. How does the database do this? The most naïve way is to sequentially scan all the records on the disk until the desired record is found. This operation has O(n) time complexity — if the database size doubles, the query time doubles as well. That is not great. We need special data structures that sp…
🙏1
Before we dive into the data storage structures, I want to set some expectations. The feedback on the relational databases post showed that people are interested in real-world, hands-on examples of how different companies use different technologies. One can directly apply this knowledge in his work, and this is great. I plan that most of the posts on the channel will contain such information. On the other hand, it i…
Dmitriy Melnik on System Design pinned «Why study system design? Reason #1: to become a better software engineer. Yes, it is that simple. Software engineering is all about trade-offs. You have to know your options to design a solution that solves business problems in the best possible way. The…»
Showing the 12 most recent of 20 posts we hold for @drim_system_design_channel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
What cloud providers do you use? Multiple answers possible.
The shares total 138%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 6 April 2021 to 12 December 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
@drim_system_design_channel named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Dmitriy Melnik on System Design” (@drim_system_design_channel), 232 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/drim_system_design_channel.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.