Channel
@BackendPortal
On this record: Growth · Engagement · What this channel posts · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,281subscribers
-41 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001633059299 |
|---|---|
| Type | Channel |
| Username | @BackendPortal |
| Description | Присоединяйтесь к нашему каналу и погрузитесь в мир Backend-разработки Связь: @devmangx РКН: https://clck.ru/3FobxK |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/BackendPortal |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:14 | 16,281 | -29 |
| 11 Aug 2026, 14:57 | 16,310 | +2 |
| 10 Aug 2026, 16:53 | 16,308 | -10 |
| 9 Aug 2026, 20:12 | 16,318 | +4 |
| 8 Aug 2026, 18:37 | 16,314 | -6 |
| 7 Aug 2026, 18:34 | 16,320 | -2 |
| 7 Aug 2026, 07:00 | 16,322 | no change |
| 7 Aug 2026, 06:58 | 16,322 | first reading |
32 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 32 (29 July 2026 – 12 August 2026) |
| Views total | 38,075 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:59 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnjdAYnyZ | 1 | 11 August 2026 | 11 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 32 most recent posts we hold, published 29 July 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
90% PostgreSQL в 2026 году сводится к этим 10 вещам. Всё остальное — в основном споры об расширениях. 1. MVCC + VACUUM Обновления создают мёртвые строки. Если autovacuum настроен плохо, таблицы и индексы раздуваются, а задержки постепенно растут неделями. 2. Индексы под реальные сценарии запросов Порядок колонок в составных индексах важен. Нужно понимать частичные и покрывающие индексы, а также почему ORM иногда не…
Поздравляем, вы на 1 шаг ближе к работе мечты 🥳 Осталось только прочитать этот пост, подписаться на канал и откликнуться на вакансию 😉 Avito Career* — место, где Авито делится актуальными вакансиями и стажировками для бэкенд-разработчиков. Подписывайтесь, чтобы найти ту самую работу ✨ *карьера
Я ожидаю, что «джавафикация» экосистемы Go продолжится с появлением обобщённых методов в Go 1.27. Скорее всего, в стандартной библиотеке мы не увидим лишних обобщённых абстракций. Зато сторонние библиотеки наверняка с удовольствием воспользуются этой прекрасной возможностью. 👉 @BackendPortal
Нашёл сегодня несколько совершенно безумных открытых репозиториев для Kubernetes. Они автоматически генерируют архитектурные диаграммы: 1. KubeDiagrams Строит диаграммы из манифестов, Helm, Kustomize или текущего состояния кластера. [https://github.com/philippemerle/KubeDiagrams] 2. k8sviz Читает текущее состояние namespace и генерирует диаграмму через Graphviz. [https://github.com/mkimuram/k8sviz] 3.…
Яндекс анонсировал deep tech night — конференцию о вызовах, с которыми IT-индустрия сталкивается в эпоху AI. В программе — разговор о разработке, ML, инфраструктуре и данных на примере реальных инженерных задач. Приглашенный спикер Мо Гавдат, ex-Chief Business Officer Google X, расскажет, как генеративные нейросети меняют будущее разработки, процессы и роли в командах. Алексей Гусаков, CTO Бизнес-группы Поисковых с…
Чтобы хорошо разобраться в Kubernetes, свой кластер не обязателен. Нашёл репозиторий с 50 практическими лабораторными по Kubernetes, которые можно запускать прямо в браузере. → работа с kubectl вместо простого чтения документации → Pods, Deployments, StatefulSets, DaemonSets → HPA, scheduling, taints и tolerations → RBAC, Secrets, namespaces и quotas → Services, Ingress и реальные сценарии отладки В браузере подни…
Мгновенно клонируйте любую базу данных Postgres для быстрой разработки, тестирования и CI-пайплайнов. https://github.com/postgres-ai/database-lab-engine 👉 @BackendPortal
Если достаточно долго работать с базами данных, рано или поздно столкнёшься с проблемами подключений или параллелизма. В такой ситуации не стоит просто повышать лимиты в конфигурации. Лучше разобраться в архитектуре, чтобы понимать, почему это происходит и как исправить проблему оптимальным способом. Эта статья от гениального человека — отличный разбор управления подключениями в Postgres и возможных решений. Легко…
Один из моих любимых инженерных блогов — DoltHub. Их материал про prolly trees очень хорошо объясняет, как можно встроить контроль версий прямо в движок хранения: контентно-адресуемые узлы, структурное разделение данных, деревья, не зависящие от истории изменений, и diff, который пропускает неизменившиеся поддеревья вместо полного сканирования базы. Особенно интересно сейчас следить за DoltLite — SQLite с нативным …
Algorithms Джеффа Эриксона — одна из лучших книг по алгоритмам. Иллюстрации в ней просто отличные. Очень рекомендую. https://jeffe.cs.illinois.edu/teaching/algorithms/ 👉 @BackendPortal
Криптография — одна из недооценённых сильных сторон Go. Стандартная библиотека включает множество криптографических алгоритмов. Все они хорошо написаны, подробно документированы, достаточно компактны и тщательно проверены. Некоторые из них ещё и очень быстрые. Например, для одного из этапов SHA-256 Go использует платформенно-зависимый ассемблер. Моя реализация на Solod даже с Arm-интринсиками SHA-2 работает приме…
5 советов по Docker, которые сэкономили бы мне полгода на борьбу с раздутыми образами. 1. Используйте slim-образы python:3.11-slim вместо python:3.11. Размер образа может сократиться примерно с 1 ГБ до 150 МБ. 2. Правильно располагайте инструкции в Dockerfile То, что меняется редко, размещайте в начале. Код приложения — ближе к концу. Так кэш Docker используется эффективнее, а сборка проходит быстрее. 3. `.doc…
Showing the 12 most recent of 32 posts we hold for @BackendPortal. 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.
@BackendPortal edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 506,294 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Backend Portal | Программирование” (@BackendPortal), 16,281 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/BackendPortal.
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.