Abhay Girnara

Go Yousuf Z. !! Check out his latest blog post on elasticsearch!

11

My team and I were brainstorming the backend architecture of one of our core systems at Zomato. While creating the HLD diagram, we kept adding the most intuitive microservices and their interactions within the mesh. At this stage, we were only thinking in terms of abstract functionalities that these services would offer. Meanwhile, one of the team members proposed why we couldn't combine three (out of N 😛) services and just create one for now. From a bird's-eye view, it felt not so convincing. He explained the rationale by justifying the similarity in functionalities, flows, and data modeling. Trust me, that was not so intuitive when we were putting those three white boxes in the HLD diagram. I still had concerns about the independent scalability of those three pieces and possible challenges due to noisy neighbor issues. We asked ourselves a question: "What business outcomes do we expect from this system?" Ultimately, we got convinced with the suggestion of a merger. Learnings: 1) Technical experience in a business domain matters. Identifying similarity would have been a non-trivial job for someone who had not worked with those systems in the past. 2) Engineering efforts should (also) be traded off against the business outcomes. Engineers working in silos without a business goal generally end up overengineering the system. 3) For leads, leverage the technical expertise of your team members. Avoid being an expert in every aspect. #engineering #architecture #business #datamodeling #backend

939

24 Comments

Building a composable solution requires a robust orchestration layer to avoid creating too much dependency on one solution or any one vendor. Similarly, using vendor-provided solutions will ultimately tie you up with their solution and defeat composability. At Assurex, we built Assure.Mart, a comprehensive solution which works along with your chosen vendors, be it CMS, Commerce, CDPs, Marketing Automation platforms, and Digital Asset Management platforms. Best of all, it provides a robust plug-and-play solution without compromising on SaaS-capable features offered by the platform. Don't let your implementation defeat composability. And if you want to see all this in action, drop a note at -> bit.ly/assure-me and request a customized demo. . . . . . . . #Assurex #CRO #MarketingStrategy #Innovation #DigitalTransformation #commerce #cdp #personlize #search #accelerators #dxp #delhi #dubai #delaware #london #uae #uk #india #usa #seamless #saudiarabia #middleeast #microsoft #google #aws #technology #experience #azure #composable #startups

20

🕒 Looking for a reliable, open-source time tracker? Meet Kimai 💡! It's a powerful, free tool that handles freelance and business projects with ease. 🚀 Kimai's impressive features include: ✅ JSON API, invoicing, data exports ✅ Multi-timer & punch-in punch-out mode ✅ Tagging, multi-user, multi-timezones, multi-language (30+ translations!) ✅ Authentication via SAML/LDAP/Database, two-factor authentication (2FA) ✅ Customizable role and team permissions ✅ Responsive design, user/customer/project specific rates ✅ Advanced search & filtering, money and time budgets ✅ Advanced reporting, plugin support ...and so much more! 🔧 System requirements: PHP 8.1.3, MariaDB/MySQL, webserver & subdomain, PHP extensions 🚀 Either set up natively with Git and Composer, or use Docker containers. Host it on your local machine, shared hosting, Synology, or hosted environments. If you'd rather not host yourself, check out the Cloud version! 🔄 Updating and maintaining Kimai is a breeze, with regular release versions and easy-to-follow upgrade steps 📚. 👉🏼 [Documentation](https://lnkd.in/g8xuNwVg), [blog](https://lnkd.in/gSyf9hpk), and [plugins](https://lnkd.in/g3_caFCF) are all available. #OpenSource #TimeTracking #Kimai #Productivity #TechCommunity

7

🔧 Ever found yourself in a situation where tracking time spent on projects or tasks became a challenge? Meet Kimai, an open-source, professional-grade timetracker that can help you manage your time more efficiently! 🌟 Key Features: ✅ JSON API ✅ Invoicing ✅ Data exports ✅ Multi-timer & punch-in/punch-out mode ✅ Tagging ✅ Multi-user, multi-timezone, multi-language (30+ translations!) ✅ SAML/LDAP/Database authentication ✅ Two-factor authentication (2FA) ✅ Customizable role & team permissions ✅ Responsive design ✅ User/customer/project specific rates ✅ Advanced search & filtering ✅ Money & time budgets ✅ Advanced reporting ✅ Plugin support ...and so much more! 📚 I've personally found Kimai to be an invaluable tool in organizing my projects and tracking time. With its robust feature set and ease of use, it has made time management a breeze! 💬 I'd love to hear your thoughts and experiences with time-tracking tools. Let's start a conversation and learn from each other. Don't forget to include the hashtags #Kimai #TimeTracking when sharing your thoughts!

6

We dedicated significant effort over the past 2 quarters to optimize our cloud costs, aiming to reduce unnecessary expenses while maintaining performance. AWS offers great cost-effectiveness, yet underutilized resources and inefficient configurations can result in wasted spend. Key strategies for our AWS cost optimization were: ✅ Right-sizing resources based on workload demands ✅ Choosing suitable pricing models (On-Demand, Reserved Instances, Spot Instances) ✅ Streamlining storage and database expenses ✅ Deploying auto-scaling and scheduling ✅ Regularly monitoring usage and costs Through these strategies, we could achieve: 🚀 Up to 35% optimization in AWS costs 🚀 Enhanced resource utilization 🚀 Improved financial governance and transparency 🚀 Unleashed cost savings for innovation and growth It's crucial to note that cost optimisation is an ongoing journey, necessitating continuous monitoring and adjustments to maximise AWS cost savings. Kudos to Shashikant Bandgar Mohit Kaushal Rohit Laddha Priyesh Mishra Hitesh Sharma Priyank Chandariya Adarsh Singh Sunny Dev Abhijith Krishnappa Nipul Sawant Arvind Srinath 🚀🚀 That said, here’s a peek into our journey of optimising Licensed ES to self-hosted on K8S. Kudos to Shubham Setia Sameer Sharma & Ritesh Bharti 🚀

46

Calling all enterprises and startups building for Bharat, crafting MultiLingual Voice and Text experiences- Reverie Language Technologies is launching its new API platform on December 12!! If you are building AI agents, Omni-channel bots or web apps for any of the marketing and support use cases, Get free credits of our Speech and GenAI APIs, Try them out in our Playground and integrate in your solutions in no time! Reverie Language Technologies Vivekanand Pani Swati Shukla Bhaskar Soham Bhattacharya #speechtotext #asr #indianlanguagecomputing #buildingforbharat

14

Why does all technology reduce down to software? #AskGPT #SoftwareEatsEverything The assertion that all technology reduces down to software reflects the growing integration of software into various technological domains. Here are some reasons why this is often considered true: 1. Control and Functionality: Software dictates how hardware operates, controlling everything from simple devices to complex systems. Without software, hardware is often inert or limited in functionality. 2. Flexibility and Adaptability: Software can be easily updated, modified, or reconfigured, allowing for rapid innovation and adaptation to changing needs, unlike hardware which often requires physical alterations. 3. Integration of Systems: Many technologies rely on software to connect and coordinate different hardware components, enabling interoperability between devices and systems (e.g., IoT devices communicating over a network). 4. Automation and Intelligence: Software allows for automation of processes and integration of artificial intelligence, enhancing the capabilities of technology by enabling complex decision-making and data processing. 5. User Experience: The software is essential for user interaction with technology. Operating systems, applications, and user interfaces determine how effectively users can utilize hardware. 6. Data Management: In today’s tech landscape, software is crucial for collecting, processing, and analyzing data, which is at the core of modern technologies like big data, machine learning, and cloud computing. 7. Digital Transformation: Many industries are undergoing digital transformations, where traditional processes are increasingly replaced by software-driven solutions, blurring the lines between hardware and software. Overall, while hardware is essential for physical technology, software provides the intelligence, flexibility, and user interface that makes technology functional and relevant in a rapidly evolving digital world.

2

🚀 Excited to dive into the world of system design interviews? Here's a quick guide to get you started: Understand the Basics: Grasp the fundamentals of system design principles like scalability, reliability, and maintainability. Solidify your knowledge of data structures and algorithms. Practice, Practice, Practice: Get hands-on experience by solving real-world design problems. Leverage platforms like LeetCode, HackerRank, or Grokking the System Design Interview. Know Your Patterns: Familiarize yourself with common system design patterns such as Client-Server, Pub-Sub, and MapReduce. Recognizing these patterns can streamline your problem-solving process. Stay Updated: Keep pace with industry trends and best practices. Follow blogs, attend webinars, and join online communities to stay informed about the latest advancements in system design. Communicate Effectively: Practice articulating your thought process clearly and concisely. In interviews, focus on explaining your approach, considering trade-offs, and justifying your design decisions. Below are five common system design questions :: 1. Design a URL shortening service (Tiny URL) 2. Design a chat system (Slack/WhatsApp) 3. Design a ride sharing service 4. Design a content delivery network(CDN) 5. Design a parking lot system Remember, system design interviews are not just about finding the perfect solution but also demonstrating your problem-solving skills and communication abilities. Happy designing! 🛠️ #SystemDesign #InterviewPrep #TechCareer

6

Want to Improve Code Quality? Here Are the Metrics That Matter! 🧑‍💻 Blog link 👉 https://lnkd.in/g3UtbwT2 Here are 4 metrics to get you started: 1. Cyclomatic Complexity ➜ Tracks complexity by counting logic branches. (Lower is better!) 2. Dead Code ➜ Find & remove unused functions, classes, methods, imports, exports & files 3. Code Duplication ➜ Duplicates waste time. Keep it DRY (Don’t Repeat Yourself) 4. Code Governance ➜ Enforce language & company-specific checks on every commit P.S. Which metric are you focusing on?

24

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

318

27 Comments

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

Design systems as if you were the one who will maintain them. Few nuggets to keep handy, while designing a scalable system: https://lnkd.in/g_udCNm3 #systemdesign #scalability #performance

15

Here's a summarized LinkedIn post reflecting the question being asked in Ness interviews: 💡 Custom Components: A Key Topic in Ness Interviews Hi LinkedIn network, During an interview with Ness, I was asked about custom components in Angular—how they are created and implemented. Custom components are reusable, modular UI elements that simplify code and enhance maintainability. For example, I shared how I implemented a custom component with four configurable text boxes, making it adaptable and reusable across applications. Have you faced similar questions in interviews? I’d love to hear your thoughts or tips on tackling such topics effectively! #Angular #CustomComponents #InterviewPreparation #Ness #FrontendDevelopment

1

I fully believe in this even though I am a tester. We are always late. We should focus more on defect prevention rather than simply defect reporting. #testing #automation #softwareengineering

11

5 Comments

Our democracy is feudalism + Right to adult franchise. A leader can block as much fast moving traffic in Mumbai suburbs for some road show. Outcome, thousands of not millions are trapped in traffic for 5 hours. - A police officer can hit general public at its will even if he demand legitimate things -Without corruption no government work is possible. -After paying close to 40% tax on purchase of a Mid Size SUV, you can’t escape the vicious cycle of pothole roads. - You become Neta, Babu or contractor. You are set for entire life without any work and accountability. - Judicial Inconsistency is sine qua non virtue of Indian judiciary. Where jurisprudence vary as per your power and money. - Everyone looks down on other in term of social capital which derives its worth from money and muscle power. - country not able to build single city which is liveable. Fully blackpilled can’t see any hope of improvement as I am watching election discourse. 

4

It is practically impossible for developers to explain each and every change that they made to the application. Even if they do, they will forget to mention few things. Below are the alternatives that you have to know about the change. 1. Setup some regular dedicated calls to go over the changes going in the upcoming release. 2. Talk about what is happening on a daily call. 2. Go through all the JIRA that is tagged for upcoming release and ask relevant questions to understand it. It is important to understand even those jiras's which are pure tech only like some upgrades to library etc. You should atleast at high level know why they did that change. 3. Attend pull request review calls. 4. Go over all the pull request code change at your own pace. 5. Run all your automated test suites atlease once a day and analyse each failure as to why it failed. #testing #automation #softwareengineering

39

5 Comments

🚀 System Design Archive: Your Ultimate Guide to Scalable Systems System design is the backbone of building applications that are scalable, resilient, and efficient. Whether you're prepping for interviews or creating the next big thing, this book is your go-to resource. 📘✨ 📖 What’s Inside? ✅ API Mastery: Learn 9 types of API testing and discover the best ways to boost API performance. ✅ Architecture Insights: Explore resilient architectural patterns, distributed systems, cloud design, and sharding strategies. ✅ Tech Stacks Unveiled: See how tech giants like Netflix and Uber scale their systems. ✅ Cheat Sheets Galore: Visual guides for cloud databases, CI/CD pipelines, and more! 🌟 Why You Need It ⚡ Perfect for developers and architects at every level. ⚡ Tailored for both quick learning and deep dives. ⚡ Packed with real-world examples and actionable tips. 💡 My favorite takeaway? 👉 Always revisit your architecture! System evolution isn’t a one-time decision—it’s a strategy. What’s the most fascinating system design concept you’ve come across recently? Let’s discuss in the comments! 👇 Follow Madhu K. for more tech insights and system design tips! 🔗✨ Credits: ByteByteGo #SystemDesign #TechInsights #APIDesign #CloudComputing #TechLeadership #SoftwareEngineering #DistributedSystems #Scalability #ArchitectureDesign #DeveloperTips

20

3 Comments

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