Channel
@dev_ops_info
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,184subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001160904474 |
|---|---|
| Type | Channel |
| Username | @dev_ops_info |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/dev_ops_info |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 02:17 | 2,184 | -1 |
| 3 Sept 2026, 10:09 | 2,185 | -3 |
| 28 Aug 2026, 00:04 | 2,188 | -3 |
| 25 Aug 2026, 07:43 | 2,191 | +2 |
| 22 Aug 2026, 17:47 | 2,189 | -3 |
| 19 Aug 2026, 09:38 | 2,192 | -1 |
| 16 Aug 2026, 20:16 | 2,193 | +2 |
| 13 Aug 2026, 12:34 | 2,191 | +3 |
| 10 Aug 2026, 13:07 | 2,188 | +1 |
| 7 Aug 2026, 21:43 | 2,187 | -1 |
| 7 Aug 2026, 00:46 | 2,188 | first reading |
20 posts held, back to 1 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 13 April 2026. An engagement rate over an empty window would be a number about nothing.
11 принципов обеспечения надежности, которые технический директор усваивает слишком поздно Прагматичный подход к обеспечению надежности для стартапов, согласно которому стремление к высоким показателям бесперебойной работы (99,99 %+) — это ловушка с экспоненциально растущими затратами, которая снижает скорость разработки до того, как продукт будет готов к выходу на рынок. Ключевые принципы: каждые дополнительные дев…
ПРЕКРАТИТЕ изучение Kubernetes (сначала сделайте это) для 70% вакансий в сфере DevOps не нужны глубокие знания Kubernetes. Нужны базовые знания об облачных технологиях, CI/CD и инфраструктуре как коде. Для большинства приложений Kubernetes — это излишество. Но вот в чем проблема: рекрутеры указывают «Kubernetes» в каждом описании вакансии, потому что это модное словечко. https://www.youtube.com/watch?v=keZN3i23qXs
Как определять и использовать обработчики в Ansible Playbooks https://www.digitalocean.com/community/tutorials/how-to-define-and-use-handlers-in-ansible-playbooks
О чем следует подумать при докеризации приложения https://nickjanetakis.com/blog/things-to-think-about-when-dockerizing-your-app
5 продвинутых проектов AWS, которые помогут вам получить работу (2025) https://www.youtube.com/watch?v=JxrnMimc478
Я создал первую систему мониторинга для своей компании — вот чему я научился https://medium.com/data-science-collective/i-built-my-companys-first-monitoring-system-here-s-what-i-learned-bed76942cc72
Почему мне нравится использовать Docker Compose в продакшене https://nickjanetakis.com/blog/why-i-like-using-docker-compose-in-production
Лучшие инструменты мониторинга приложений для разработчиков https://www.freecodecamp.org/news/top-application-monitoring-tools-for-developers
Учебник по написанию скриптов на Bash для начинающих https://www.youtube.com/watch?v=PNhq_4d-5ek
5 проектов, которые действительно сделают вас лучше в Docker https://dev.to/code42cate/5-projects-that-will-actually-make-you-better-at-docker-5108
Что нового в PostgreSQL 18 — точка зрения администратора баз данных (чтение занимает 5 минут) PostgreSQL 18 beta 1 представляет асинхронную подсистему ввода-вывода, которая обещает увеличить пропускную способность ввода-вывода, особенно для пользователей Linux, использующих io_uring. Также в обновление включена встроенная поддержка UUIDv7, улучшения команды EXPLAIN, возможность добавлять ограничения NOT NULL как NOT …
Awesome Docker Compose — ваш центр поиска и развертывания более 700 популярных приложений с самостоятельным размещением без усилий. Docker Compose, бесплатный инструмент с открытым исходным кодом, упрощает процесс, автоматически обрабатывая зависимости и службы, позволяя вам устанавливать любимые приложения без обычных хлопот. https://awesome-docker-compose.com/
Showing the 12 most recent of 20 posts we hold for @dev_ops_info. 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.
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 1 registered channel — 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.
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 2 seed channels' Telegram-generated recommendation lists 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Devops” (@dev_ops_info), 2,184 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/dev_ops_info.
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.