Telegram RegisterThe public register of Telegram
Telegram profile photo for Ashish's Channel

Channel

Ashish's Channel

@ashishsingh_channel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

46subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001462899179
TypeChannel
Username@ashishsingh_channel
DescriptionEntrepreneur, Investor, and Data scientist. I post 1 good article on investing and related topics every day. Twitter: https://twitter.com/siashish_
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held2
On Telegramt.me/ashishsingh_channel

Growth

467 August 2026 — 46 subscribers10 August 2026 — 46 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 45–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 14:3146no change
7 Aug 2026, 20:1646first reading

Engagement

17 posts held, back to 1 January 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 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 17 posts for this entry, the most recent from 25 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
87
Videos
8
Links
236

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

4 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4100.0%

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 3 of the 17 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 1 January 2025 to 25 March 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

25 Mar 2025, 05:31 UTC56 views2 reactionsread 10 August 2026
Photo

🔹 Best Practices for Distributed Data Management in Microservices 🔹 Managing data in a microservices architecture comes with challenges like consistency, scalability, and resilience. Here are key best practices: ✅ Database Per Service – Each microservice should have its own database to ensure loose coupling. ✅ Event-Driven Communication – Use messaging systems (Kafka, RabbitMQ) to maintain eventual consistency. ✅ …

👍2

Signed Ashish Singh

12 Mar 2025, 15:51 UTC52 views1 reactionsread 10 August 2026
Photo

🚀 Saga Patterns & Workflow Orchestration: Managing Distributed Transactions In a microservices architecture, handling transactions across multiple services can be challenging. Here’s how Saga Patterns help: ✅ Two Types of Sagas: 🔹 Choreography – Each service triggers the next step independently. 🔹 Orchestration – A central controller manages the workflow. ✅ Why Use Sagas? 🔹 Ensures eventual consistency across s…

👍1

Signed Ashish Singh

14 Feb 2025, 23:28 UTC44 viewsread 10 August 2026
Forwarded from @linkedin_learning_academyPhoto

💡 The Power of quiet People 📤 Join Linkedin Learning Academy for more courses 🔔 Subscribe my Youtube channel and System Design Newsletter for more valuable contents

Signed Ashish Singh

13 Feb 2025, 06:55 UTC37 views1 reactionsread 10 August 2026
Photo

🚀 𝐄𝐯𝐞𝐧𝐭 𝐒𝐨𝐮𝐫𝐜𝐢𝐧𝐠 & 𝐂𝐐𝐑𝐒: 𝐀 𝐏𝐨𝐰𝐞𝐫𝐟𝐮𝐥 𝐃𝐮𝐨 𝐟𝐨𝐫 𝐒𝐜𝐚𝐥𝐚𝐛𝐥𝐞 𝐒𝐲𝐬𝐭𝐞𝐦𝐬 Event Sourcing and CQRS (Command Query Responsibility Segregation) are two architectural patterns that enhance scalability, consistency, and auditability in large-scale systems. Here’s a quick breakdown: 🔹 Event Sourcing – Stores every change as an immutable event instead of just the latest state. Enables auditability, event replay, and better fault toler…

👍1

Signed Ashish Singh

7 Feb 2025, 10:56 UTC32 viewsread 10 August 2026
Photo

🚀 Event-Driven Architectures: Building Scalable & Decoupled Systems Event-driven architectures (EDA) enable highly scalable, responsive, and loosely coupled systems by reacting to events in real-time. Here’s a quick breakdown: 🔹 What is EDA? A design pattern where components communicate by producing and consuming events instead of direct calls. 🔹 Key Benefits: ✅ Scalability – Easily handle high traffic with async…

Signed Ashish Singh

26 Jan 2025, 05:03 UTC27 viewsread 10 August 2026
Photo

Guided by the wisdom of our history and the spirit of patriotism, let’s honour our nation. Happy Republic Day. 🇮🇳#RepublicDay

Signed Ashish Singh

24 Jan 2025, 12:01 UTC26 viewsread 10 August 2026
Photo

🌍 Multi-Region Architectures: Building Globally Scalable and Resilient Systems Key takeaways: 1️⃣ What is it? - Deploying application components across multiple geographic regions to ensure low latency, high availability, and fault tolerance. 2️⃣ Benefits: - Low Latency: Serve users closer to their location for faster response times. - High Availability: Maintain uptime even during regional failures. - Disaster Rec…

Signed Ashish Singh

17 Jan 2025, 07:38 UTC35 viewsread 10 August 2026
Photo

🚦 Master API Traffic with Rate Limiting and Throttling Effectively managing API traffic is key to building resilient and high-performing systems. Here's a quick overview: 1️⃣ Rate Limiting - Restricts the number of API requests within a given timeframe. - Ensures fair resource usage and protects against overloading. - Examples: Fixed window, sliding window, token bucket. 2️⃣ Throttling - Slows down traffic instead …

Signed Ashish Singh

13 Jan 2025, 15:15 UTC26 viewsread 10 August 2026
Photo

🌐 A Closer Look at Replication and Failover Strategies In system design, ensuring resilience and availability is crucial. Here's a quick breakdown: 1️⃣ Replication: - Creates copies of data across multiple servers. - Benefits: High availability, fault tolerance, and improved performance. - Types: - Synchronous: Strong consistency but higher latency. - Asynchronous: Faster writes with eventual consistency. 2️⃣ Fai…

Signed Ashish Singh

12 Jan 2025, 12:02 UTC26 viewsread 10 August 2026
Photo

Check this out! https://youtu.be/ffIdM2kDq1Y

Signed Ashish Singh

9 Jan 2025, 04:19 UTC28 viewsread 10 August 2026
Photo

Check this out! https://youtu.be/h0z7yteUOes

Signed Ashish Singh

7 Jan 2025, 14:54 UTC28 viewsread 10 August 2026

🌟 Designing for High Availability: Building Systems That Never Go Down In today’s always-online world, high availability (HA) is essential for user trust and business success. Here's a quick overview: 1️⃣ What is High Availability? - Ensures your system stays operational with minimal downtime, even during failures. 2️⃣ Core Principles: - Redundancy: Duplicate critical components to avoid single points of failure. -…

Signed Ashish Singh

Showing the 12 most recent of 17 posts we hold for @ashishsingh_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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

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.

Cite this entry

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Ashish's Channel” (@ashishsingh_channel), 46 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ashishsingh_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.