Rajesh Nair

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 India’s digital public infrastructure is enabling the emergence of state-backed ‘alt big tech’ "India Stack" Much of what was described as digital public infrastructure in this context flowed from India’s experiences with projects like Aadhaar for digital identification, the Unified Payments Interface for digital payments, and more recently, the account aggregator framework for data management in the financial sector. A host of such interventions built around the idea of standardisation of “open” application programming interfaces, or APIs, are collectively described as the “India Stack”. #digitalindia #upi #DPI #bigtech https://lnkd.in/g7tqyjSe

8

How do you become a better programmer while being an SRE? Many SigNoz users and customers are SREs and DevOps engineers. In my conversations with them sometimes they lament the fact they don’t “code” any longer and want to sharpen their edges by writing application code. But they rarely get a chance to do this at their job. Coding is also like building a muscle. If you go months and months without writing any application code, when you do finally need to write code, suddenly you will find that you have lost the muscle. It's like not benching for a year and then trying to bench press. (Infrastructure-as-code is a different muscle entirely, and more config files than code). While strictly speaking SRE job does involve writing code - scripts, yaml, etc. IS CODE. But to those who miss writing application code, here’s some tips on getting started: 1. Pick a language you want to code in first, decide a hobby project and build it from end to end. With AI assistants like ChatGPT and CoPilot easily available now, an easy way is to chat with the LLMs to develop a plan and build the project. They can act as a sparring partner for you and also help in rubber ducking or resolve errors which may come up 2. Contribute to an open source project : One problem with doing something which is not part of your main job is to keep yourself motivated an accountable. I find open source communities to be a great way to help in this. Rather than choosing a hobby project of your own, you can just choose to work on a open source project. Start asking questions, joining community calls and interacting on Github/Slack. You will find problems in the project that need to be solved - and you can raise your hand to solve it. The advantage is you have people in the community to help you if you get stuck and if your PR gets accepted finally then you have a “greener” github profile to show for 🙂 3. Practice Leetcode everyday : For people who want something more piecemeal, leetcode could be great way to start. Agree it is not strictly application code, but it still helps you solve problems with code. And if you agree that writing code is like building a muscle, Leetcode is doing 10 pushups everyday. It is not tough to do - but if you do it everyday, you are on your way. 4. Build sample apps and demo projects for your team : This may not be applicable to all teams, but if you work in a developer focused product (like SigNoz) your team may need sample apps for their docs and demos. Raise your hand when you get such an opportunity. 5. Study books on design patterns and check code structures of open source projects: While this is not as good as “writing code”, if you really can’t get time to put keystrokes to your code editor, just start reading how other open source projects are solving problems. Studying more about design patterns and their application in real projects will help you get the juices flowing and who knows may give you enough motivation to get started 🙂

53

6 Comments

A super clear, straight forward example of how to do cost effective RAG using LangChain for your document pipeline and Groq for compute resources. The code demonstrates how to speed up RAG and reduce costs using quantized embeddings (reducing 32 bit values to 8) Nice job Sahibpreet Singh! https://lnkd.in/gf5QMCKK

44

2 Comments

Three years back, I was working as the CTO at a late-stage company where our cloud infra had become too complex – owing to multiple environments, acquisitions, and multi-region deployments. Our tooling was not standardized and different teams worked on different tech stacks, leading to duplication of effort and slow releases. . We tried all the prescribed solutions. We adopted Kubernetes. We went with IAC. But none of these addressed the challenges to the core. We needed something with an architecture-first approach – something that was cloud-agnostic and formed the basis of every deployment – across teams, regions, and clouds. But, since a solution like this didn’t exist in the market, we built it in-house. We thought this could benefit other companies as well, so I, along with Anshul Sao and Rohit Raveendran, branched out and built Facets.cloud. We got some early validation through paying customers, raised a round of funding, and thought we were on the right track. Over the last three years, we have built one of the largest feature sets in the DevOps automation space. Everything from designing architectures to launching environments to managing releases and having pre-configured observability setups for every project. Our vision was that developers should be able to self-serve their infra. But, through various conversations with companies of all sizes – we realized two things. -We’ve built a mammoth product that’s very complex to understand  -Our users (developers) need something they can try before buying Biased by our own experience working at a company that sold to enterprises, we’d ended up building a bloated enterprise product that hadn’t gone through the rigor of ruthless user feedback. Today, we are taking a big step to fix that error. We are building Facets 2.0, an easy-to-use tool for devs to deploy their apps to the cloud real quick. Over the next few weeks, we’ll be stripping down our giant DevOps automation platform to rebuild something any developer or DevOps engineer could use. While we continue to serve enterprises, we now have the exciting prospect of working with early/growth stage startups and solve for usability. We are inviting Beta testers. If you or anyone in your team would like to try out the product and give feedback, please reach out to me or you can become a beta tester through this link. (https://lnkd.in/gXYTS5Bx). Your feedback is greatly appreciated. Stay tuned as I share our journey. #buildinpublic Mohita Nagpal (she/her) Prashant Dhanke

352

35 Comments

One of the key capabilities that sets Memgraph apart from the competition is our deep path traversal algorithms. Come read our latest blog explaining all about it: https://lnkd.in/gBtWPJuZ

27

2 Comments

The wait is almost over 😃 Just 1 day to go for SigNoz Launch week 2.0! Observability cost is one of the biggest concerns of engineering leaders. We have seen users come to us after being ripped off by unpredictable pricing—pricing that doesn’t make sense for modern cloud-native services. At SigNoz, we dived deep into these concerns and addressed them in our pricing plan: 👉 Simple usage-based pricing - you pay only for the data you send 👉 Add unlimited team members - we find it weird that observability vendors charge for user seats. Any dev can need debugging, so we don’t charge for user seats. 👉 No Host (container or node) based pricing - For modern cloud-based applications it doesn’t make sense to charge on the basis of number of hosts or containers. You don’t need to worry about auto-scaling during peak hours. 👉 No special pricing for custom metrics - At SigNoz, you can send any application or business metric and pay the same amount as other metrics Join us for a week for exciting new features - link in the comments 👇

36

2 Comments

♾️ Sreeram Kannan breaks it down: The state of the EIGEN universe, restaking, data availability, and building humanity's coordination engine with EigenLayer. More on Twitter ↓ https://lnkd.in/gQZhUf8T

2

Good read

1

INDstocks by INDmoney saw almost 3x scale of concurrent users using the application through the last 3 days. As #India was getting prepared for its much awaited #generalElectionResults, the Engineering team at INDmoney embraced this challenge of getting ready for humungous scale. While many brokers had issues scaling for this traffic surge, primarily on June 3 (Monday), #INDstocks was quite resilient and gave all it's users highly reliable trading experience on all the three days (June 3 - 5). We have achieved this through a lot of best practices in #Engineering. All our Backends are independently scalable micro services, which gives us greater flexibility. We decoupled core components to a large extent, which allows seamless experience to our users on both Apps and website, even in the events of unprecedented scale. On days when volatility hits through the roof, an ultra-efficient square-off system which protects users from going into dangerous circuits and thereby losing money, is of paramount importance. Through our #INDprotect feature, our users' square-off orders were sent to exchanges in under 5 ms, which helped users reduce their losses significantly! At the market open, we saw close to 50% more price ticks from exchanges on June 4 and INDstocks users didn't have to face any latency in viewing the live prices on their web / mobile devices. Our #superFast #Pricer delivered all the ticks to users in under 1ms. #INDmoney #INDstocks #Election #Buzz #IndianEquities #Stock #Market #Economy Ashish Kashyap Nikhil Behl Mourya Venkat vasu choudhary Ashwin Sreekumar Sonu Singh Tejas Chhotani Deepak Gupta Kartikay Aggarwal Tushar Kumar Singh Deepak Pandey Nikhil Choudhary Sivajee Battina Pooja MD Harsh S. Aniket Pathak

218

8 Comments

Is Perplexity over before it’s begun? Solo developer recreated it and made it open source… allegedly over a weekend https://lnkd.in/g9RZTP9p Perplexity’s investors are pushing for it to be the next Google in terms of search, which in all fairness is something investors have been trying for the better part of two decades, propping up new entrants. But the recent investigations from AWS over the Robots.txt crawler scandal and lawsuits from publishers Wired and Forbes makes for a rocky future. Personally, I think large action models is the necessary pivot. Apple’s on-prem AI direction is the only sane strategy I’ve seen coming out for consumer AI. Thoughts?

8

3 Comments

Until a year ago I had a bias, 'Kubernetes is only relevant for late-stage companies'. During our market research, we were surprised to see startups as small as 20 employees using Kubernetes from day 1. Vedant Vyawahare & I have seen multiple reasons why companies moved to Kubernetes: 1. Serving unpredictable markets like travel and e-commerce. 2. Optimizing resources and avoiding provisioning. 3. Need to leverage Cloud credits across AWS, GCP & Azure Here are a few reasons why Kubernetes is becoming a household name. If you are planning to evaluate Kubernetes, feel free to ping me or sign up for our waitlist. (Link in comments) #Kubernetes #devops #devtools

30

3 Comments

F5 has announced the general availability of F5 NGINX One, combining advanced #LoadBalancing, web and application server capabilities, #APIgateway functionalities, and security features in a dedicated package. Shawn Wormke, Vice President and General Manager for NGINX at F5, said, “App delivery and security functions—and corresponding visibility—are often sequestered among individual groups. NGINX One is ideal for modern, ephemeral, and cloud-native app components such as containers and #Kubernetes, providing a solution that cost-effectively optimizes, scales, and secures complicated application and API environments across multiple teams.” “Unlocking innovation and simplifying complexity have now been made easy with NGINX One,’’ said Pratik Shah, Managing Director India & SAARC, F5 Networks. “I’m excited to announce its launch, marking the evolution of NGINX from a stand-alone product to a comprehensive hybrid #SaaS experience, designed for the demands of modern, multi-environment applications.” “The success of microservices-based and containerized applications and app components relies on the work of many separate teams,” said Jim Mercer, IDC Program Vice President, Software Development, DevOps, and DevSecOps. “NGINX One is essentially designed to make it easier to harmonize these workflows. This release marks the evolution of NGINX from primarily a development tool to a more mature enterprise-class SaaS-based solution. As a result, customers may be able to reduce certain point solutions since they can see performance and security data across the NGINX application landscape without being limited to a single Kubernetes cluster.” . Read in detail at: https://lnkd.in/gu25_jaz . Munish Bhasin Meghan Hole Chad Whalen Jill Alm Jana Olivier, PHR, SHRM-CP Kat McClure Sriram Raja Jason Rahm Nirmal Joshi Ram Narain SINGH Adarsh Kumar . Follow SmartStateIndia for more #IndustryUpdates . #smartstateindia #f5 #networksecurity #multicloud

9

If you are thinking of becoming an EM and looking for resources, I highly recommend reading Suresh Choudhary's Diary of an EM! https://lnkd.in/dMzuFivi

6

3 Comments

So many meaningful indicators in this post: On CI: "The process has become so streamlined that the rest of the team jokes about grabbing popcorn and waiting for the magic to happen." On Dev: "In just a few hours, we can turn an idea into an internal test track for our Product Owner’s feedback, creating a feedback loop faster than ever." On Updates: "I almost forgot what RN's Upgrade Helper looked like—it's like trying to teach an old dog new tricks. Expo makes upgrades smoother than a jazz saxophonist on a Sunday morning." This is such a helpful post for developers on "vanilla" React Native apps, looking at the direction that the platform's framework architecture is headed, and realizing how to migrate. Thanks 🚗 Steve Galili for sharing MyWheels experience. Promising outcomes to say the least!

2

Has the adoption of Devsecops 𝒓𝒆𝒂𝒍𝒍𝒚 made the software delivery process 𝒇𝒂𝒔𝒕𝒆𝒓? Had an interesting conversation with Swastik Mukherjee yesterday where he mentioned that paradigms like devops and CI/CD came up to make software delivery faster but these days the cramming of 𝘪𝘯𝘯𝘶𝘮𝘦𝘳𝘰𝘶𝘴 𝘴𝘦𝘤𝘶𝘳𝘪𝘵𝘺 𝘴𝘤𝘢𝘯𝘴 in the CI and then the back-and-forth between security and developers is hampering the software delivery speeds.(Or atleast that's what the developers think). Abhishek Anand had a contrary opinion that adoption of CI(with the the tests and the security scans) actually saves time for developers later. The cost of fixing defects later in the software development lifecycle increase exponentially. {Adding in a blog which covers some old studies of NIST and IBM which mentioned the 𝘤𝘰𝘴𝘵 𝘰𝘧 𝘧𝘪𝘹𝘪𝘯𝘨 𝘥𝘦𝘧𝘦𝘤𝘵𝘴 𝘥𝘶𝘳𝘪𝘯𝘨 𝘮𝘢𝘪𝘯𝘵𝘢𝘪𝘯𝘦𝘯𝘤𝘦 𝘣𝘦𝘪𝘯𝘨 4-5𝘟 𝘵𝘪𝘮𝘦𝘴 higher than during testing phase} Another anecdote or joke i have heard is that 100% test coverage during CI itself will reduce the need of appsec teams by 80% :P I too believe that the adoption of modern devsecops practices have been amazing for both productivity and security but maybe the industry needs to do more work of convincing developers of the same? :P What do you guys think? Shivam Saraswat Abhishek Gopal https://lnkd.in/gKWrFzJm.

26

3 Comments