Vikram Babu Kuruguntla

Amazing performance improvement with usage of integrated cache . Do read more about it in the blog below. 1️⃣ Improvement in latencies. 2️⃣P75 latency is down 75% and 3️⃣ P99.9 latency is down over 67% 4️⃣ Reduced infrastructure from 60k cpu cores to 3k https://lnkd.in/g6QA4YVm

24

The more I work with #Elixir the more I come to appreciate the language and its #community. We at DAT AI Systems Pvt Ltd did a major migration from #Kafka to #AMQP without any downtime or client impact 💪. #Queues are the unsung heroes of #reliable, #scalable, and #distributed systems. With the AMQP protocol, an open standard widely adopted across industries, you can easily integrate #messaging into your stack without worrying about vendor lock-in. Why should you use queues in your architecture? - Decouple services for better scalability and resilience - Handle #asynchronous workloads efficiently - Ensure message #reliability and guaranteed delivery - Benefit from strong AMQP support across cloud and on-prem environments As businesses grow, embracing #open standards like AMQP ensures #flexibility, #portability, and long-term #stability. Ready to #future-proof your system? Check out my latest blog on the benefits of queues and AMQP. dev.to: https://lnkd.in/gDvce_nb Medium: https://lnkd.in/gVp9euNu #AMQP #MessageQueues #CloudArchitecture #Scalability #OpenStandards #EnterpriseTech #DistributedSystems

16

3 Comments

How do you achieve high availability with leader-based replication ? For achieving high availability with leader-based replication ,the system should handle both leader and follower failure . https://lnkd.in/g3wgQEZe

5

Expressing http routes in Golang is now enhanced with 1.22 Features like methods matching and wildcard matching get introduced. They have changed their precedence logic for matching patterns too. https://lnkd.in/ge8t79uE

2

Just finished recording a great podcast with Ankit Jain on his #HangerDX podcast. We chatted a lot about engineering metrics, their value, and how you should/shouldn't use them to drive change across your organization. It should be released soon, so make sure to check it out! #softwareengineeringinsights #engineeringmetrics #developerexperience

25

The journey towards gRPC starts by understanding RPC conceptually. That's what this video by Arpit Bhayani is all about. https://lnkd.in/gaUGrGGP

1

🧐Peep into the technology; #1. How does basically these live streaming apps work for a load of millions of concurrent users. ▪️ Recently came accross a fascinating news of how Netflix handled Jake Paul vs Mike Tyson fight streaming which crosses 60 million 'concurrent users' which is a new world record for any streaming platform on the planet. However it was not so smooth experience for the users they faced issues like network failure, latency in delivery , buffering etc. 🤯 But isn't it fascinating , how a single platform like Netflix, hotstar or jio can handle more than half a billion concurrent users on a real time basis, i don't think this idea ever crossed my mind before untill I got into computer science. 💡 here is what engineering technologies play their role in this process. ▪️ To summarise the basic working in 4 step process, it goes like this. 1) Camera/ Mic( basically the capturing devices.) 2) Encoder( Machine/Pc with encoding software). 3) Media server, cdn ( cloud services like Microsoft Azure , aws , Google cloud) 4) Player, Playback system. 💡Although I got overwhelmed after learning about this technology, here are the crisp points I'm sharing with you: ▪️To prepare for this type of real time concurrent userbase how the engineers prepare: ▪️1) Network testing, Application testing. ▪️2) c5 9x large machines (each having 36 Cpu's and 72 gb ram , used for load generation) ▪️3) Public Cloud Environment. ▪️4) CDN partner regions, (to avoid the shortcomings of above 2 they uses GEO DISTRIBUTORIES). ▪️5) Performance and tsunamis tests ▪️6) Chaos engineering. ▪️7) Traffic pattern using ML #cloud #aws #netflix #hotstar #cdn #livestreaming #jakevstyson ⚠️ if you really want to know how this exactly works I'm providing link for the 2 videos below, check it out it's awesome how these technologies work. https://lnkd.in/g3ieQPZd https://lnkd.in/g46qYTpE

3

Jyoti Bansal recently spoke with thenewstack to discuss developer toil and how platform engineering offers a "golden path" to boost developer productivity and shorten deployment times. For the full discussion, check out the article: https://lnkd.in/gy6j24WP #DeveloperExperience #CEO #SoftwareEngineering #DevOps #PlatformEngineering

6

Hot take: Building a business around open-source software is a lost battle. In last few months, we have seen how companies such as HashiCorp, Redis labs have faced the heat when they adopted business source licensing model. It resulted in their alternatives popping up within few days like OpenTofu, Dragonfly etc. There is no moat for such businesses because the underlying software is open-sourced which means new entrants can easily replicate what they are doing. They can sell it at a cheaper price or with a better ecosystem(if they are cloud vendors) or both. These businesses also face the dilemma of whether to merge a major improvement in the open-source or put it behind the SaaS offering. An alternative to this model is to build the business around consulting & training. The business keeps the software open sourced & provide consulting services to clients who want to use it in the most efficient manner. Pivotal has done a great job with Spring framework using this model. This way your revenue stream is not marginalized by new players easily & the core team can focus on improving the software without worrying whether it makes their core revenue model i.e. SaaS offering less attractive. Especially in the non-ZIRP era, companies are bound to reconsider where they are spending. Hence they will choose the option that burns the smallest hole in their pocket. #opensource

8

2 Comments

🚀 Excited to announce our latest blog post on #performance innovations since the #OpenSearch Project's inception! The #OpenSearch project, backed by its dynamic #community, is committed to advancing the core engine's performance in open source, emphasizing #search, #vectorsearch, #ingestion, and #storage. Dive into the journey and discoveries here! #Performance #OpenSource

7

Curious about how to automate Single Sign-On (SSO) application flows? 🚀 Dive into how we are using Playwright to automate and optimize SSO processes effortlessly at Nagarro From handling session management and time-sensitive tokens to overcoming compatibility challenges, Playwright simplifies the complexities. Explore how its features like isolated browser contexts, built-in authentication handling, and comprehensive tracing can revolutionize your SSO testing. 🌐✨ Read more about overcoming these hurdles and leveraging Playwright for seamless SSO integration in our latest blog! Stay tuned for more in this series from Bharat Garg and myself, on using Playwright to solve intricate challenges. #WebTesting #Playwright #SSOTesting

20

3 Comments

It's fantastic when the team leverages platform goodness for our customers! I love how I'm able to follow along the IPL match even when I'm on the go! As with most things we do, we had to scale what came out of the box to make this work for our customer base. Read on for practical tips on how we got there.

200

2 Comments

"Then why worry?" As humans, we often tend to worry about even the smallest things, which can take a toll on our mental well-being. Gaur Gopal Das beautifully captured this tendency in a simple yet profound flow diagram that illustrates how most of our worries are unnecessary. This diagram has become one of my go-to references whenever I need a reminder, for myself or my network, why worry? It serves as a powerful tool to shift perspective, helping us focus on what we can control and let go of the rest, ultimately fostering a more peaceful mindset. #wellbeing

54

8 Comments

A great talk from Doc Norton about re-teaming. In which he is promoting the idea of ​​changing teams more often or, at least, making those changes easier. Instead of aiming for having stable teams. One example he gives is the company Valve. At which, employees choose the team they want to work on, and they can re-decide whenever they want. This leads to competition between the best teams, projects, and ideas for employees. When employees feel being on the wrong team or working on a project they do not believe in and, therefore, want to move to a different team. Then, first, this might be a signal management should care about. And, second, why holding those employees back from switching team? In the beat case, they will perform below their capacity in the wrong environment. In the worst case, they will leave the company to join a new, external team. What do you think? Do you think teams should be stable or fluent?

3

2 Comments

Exploring Redis Scaling Techniques: From Single Node Vertical Scaling to Master-Replica Setup, Sharding, Redis Cluster, and Geo-Distributed Solutions

1

Top learnings from my discussion with Kishore Gopalakrishna - Language choice for system development should balance team expertise, hiring potential, and ecosystem maturity. A well-implemented system in a familiar language often outperforms a poorly implemented one in a "faster" language. - Distributed systems are complex - they can fail in unexpected ways, making your own computer useless. This challenge is often underestimated. Understand the failure modes. - When building new systems, design for the long-term (10 years) but plan for the near-term (2-3 years). Implement for current needs while keeping the architecture flexible for future growth. Design for long term, plan for short-medium term. - Testing distributed systems requires going beyond known test cases. Develop test frameworks that generate new scenarios automatically to uncover unforeseen issues. - Cost optimization in data systems often involves trade-offs. Kafka, for example, sacrificed transactionality and exact-once delivery for higher throughput and lower cost per log. Its all about the Trade-offs. You get some, you lose some. - When approaching problems, start with first principles. Understand why something is expensive or inefficient before trying to optimize it. Don't jump on a solution. Understand the real problem first. - Open-source success relies heavily on community building. Foster respectful communication, clear processes for resolving conflicts, and a culture of helpfulness to grow a strong contributor base. There are many communities, but only the ones with good culture thrive. - Real-time analytics can significantly boost user engagement. Even small reductions in data latency can lead to measurable improvements in user experience and product value. - When considering real-time analytics, focus on how it can improve your users' lives rather than just technical capabilities. Many support issues can be eliminated by giving users direct access to real-time data. Product isn't useful if it making users' lives better. - Innovation in data products often comes from changing perspective - instead of asking "Do we need this?", ask "How can this improve our users' experience?" This shift can uncover valuable use cases for real-time analytics. Asking the right questions will help you reach the right answers. - When building data products, consider the long-term evolution of technology. Design choices should anticipate future developments, such as improvements in network speed or storage capabilities. Keep your design extensible. - As users become more data-savvy, there's increasing demand for self-serve analytics tools. Empowering users with direct access to data can reduce support overhead and enable more informed decision-making. Empower users to do more with data quickly. ———————————————————————— In case you haven't watched the episode yet, you can watch it here: youtu.be/SmLlJmU9Daw Also subscribe if you like such discussions.

41

3 Comments

"An API is an abstraction (not a program code – class or a function) that acts like a “gate” setup by a provider for a resource (sometimes more than one resource) behind the gate. Through this gate a consumer extracts information and manipulates the resource as per provider’s rules. Provider makes money per call to this gate. Set of rules agreed between provider and consumer OR published rules by consumer (anyone who is using the gate shall comply) is called "Contract" " Let me know what you think about this definition that I have come up with. Bas Dijkstra Wayne Roseberry Pramod Yadav ?

24

24 Comments

If a 100 Mb video gets 20k views in one month, how much bandwidth do we need to serve the video? These kinds of questions are called capacity estimation questions. They are part of system design interviews. The next version of the system design judge will have capacity estimation questions. Coming soon! #SystemDesignJudge #CapacityEstimation

319

27 Comments