Mantis - AI-native platform engineering’s Post

How DDD Improved Uber’s Platform Uber’s platform faced massive complexity as it scaled. With thousands of microservices spread across different domains, managing dependencies and communication became a major challenge. To tackle this, Uber applied Domain-Driven Design (DDD) principles and shifted to a Domain-Oriented Microservice Architecture (DOMA). By defining clear Bounded Contexts, Uber separated distinct business areas, allowing each team to focus on their specific domain without being overwhelmed by unrelated concerns. This restructuring allowed for greater autonomy and clarity. By grouping related microservices within each Bounded Context, Uber introduced domain gateways as single points of interaction, reducing the need for cross-context communication. This approach minimized unintended dependencies and made the platform more adaptable. Additionally, using patterns like the Anti-Corruption Layer helped protect core domains from external system changes, ensuring a clean separation between internal and external logic. The result was a more scalable and maintainable system. DDD helped Uber transform a tangled microservices architecture into a clear, modular platform that could evolve alongside new business needs. This not only reduced complexity but also empowered teams to develop and deploy independently, speeding up innovation and reducing operational friction. That’s how DDD helped Uber turn chaos into a structured, resilient system. #SoftwareArchitecture #SoftwareEngineering #DDD #ImproveUber

new #webinar alert: Monorepos at scale: Building CI for 1,000 daily commits at Uber Uber has developed strategies to keep their builds fast and efficient, even with 1,000 daily commits and over 50 million lines of code. In this webinar, we’ll cover Uber’s approach to optimizing CI/CD processes. We’ll talk about: - Using Bazel to understand build targets and optimize CI processes. - Dynamically generating CI build steps to handle complex changes efficiently. - How Uber improved CI performance through containerized environments. - Custom tools that Uber has built to ensure performant CI. #devops #cicd #buildkite

"How Uber Manages Trillions of Transactions Every Day" Ever wondered how Uber seamlessly connects millions of riders and drivers daily? It’s not just a transportation service; it’s a technological marvel. Here’s how Uber handles trillions of transactions every day with ease: 1. Microservices Architecture: Uber’s platform is composed of independent services like driver matching, routing, and payments. This ensures scalability and fast updates without downtime. 2.Real-Time Data Processing: Uber processes live data streams using Apache Kafka, enabling instant decisions on routes, ETAs, and pricing. Every millisecond counts. Dynamic Pricing Engine: 3.Surge pricing adjusts rates based on demand, ensuring a balance between riders and available drivers. It’s algorithmic magic that works in real time. Global Scalability: With cloud-native systems and global data centers, Uber handles millions of ride requests simultaneously without breaking a sweat. Uber isn’t just a ride-sharing app—it’s a tech powerhouse ensuring smooth rides worldwide. What are your thoughts on Uber’s tech stack? Let’s discuss! read more - https://lnkd.in/g-tvXcrH

With an ever-evolving technology landscape, it’s crucial to adapt and continuously upskill to stay ahead. Recently, I delved into the advantages of Microservices architecture over Monolithic architecture and found Uber’s case study particularly insightful. 💫𝐄𝐯𝐞𝐫 𝐰𝐨𝐧𝐝𝐞𝐫𝐞𝐝 𝐡𝐨𝐰 𝐔𝐛𝐞𝐫 𝐦𝐚𝐧𝐚𝐠𝐞𝐬 𝐭𝐨 𝐬𝐜𝐚𝐥𝐞 𝐚𝐧𝐝 𝐝𝐞𝐩𝐥𝐨𝐲 𝐧𝐞𝐰 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬 𝐬𝐨 𝐞𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭𝐥𝐲? As Uber grew globally, it faced major challenges with its old monolithic system: scalability issues, tough deployments, and slow development. To solve these, Uber transitioned to a microservices architecture. 🚀 𝐓𝐡𝐞 𝐒𝐡𝐢𝐟𝐭: Uber broke down its app into smaller, independent services like trip management and payments. They used an API-first approach, Docker for containerization, and Kubernetes for orchestration. Automated CI/CD pipelines with Jenkins and Spinnaker streamlined their processes, and tools like M3 and the ELK Stack provided real-time monitoring. ✅ 𝐓𝐡𝐞 𝐑𝐞𝐬𝐮𝐥𝐭𝐬: 𝐁𝐞𝐭𝐭𝐞𝐫 𝐒𝐜𝐚𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Each service scaled independently, easing bottlenecks. 𝐋𝐞𝐬𝐬 𝐃𝐨𝐰𝐧𝐭𝐢𝐦𝐞: Automated deployments meant fewer interruptions. 𝐅𝐚𝐬𝐭𝐞𝐫 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭: Teams could innovate and deploy quicker. 💯𝐃𝐞𝐯𝐎𝐩𝐬 𝐌𝐚𝐠𝐢𝐜: DevOps practices were crucial, with automated pipelines reducing errors and infrastructure as code ensuring consistent deployments. A collaborative culture made the transition smooth. 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧: Uber’s move to microservices significantly improved its scalability and efficiency. This journey highlights the impact of microservices and DevOps in managing complex applications. #DevOps #Microservices #Uber #TechTransformation #Innovation Connect to chat more about microservices and DevOps!!

Enhancing Resilience at Scale: Inside Uber's Chaos Automation Platform How does Uber ensure your cab reaches you, come what may? Let’s understand in this post. In the dynamic world of ride-sharing, where downtime can significantly impact millions of users, Uber has taken a proactive approach to system reliability with its Chaos Automation Platform. This is how: 👉 Ensuring Stability: The platform ensures Uber’s services remain stable and reliable, even under unexpected conditions. 👉 Chaos Engineering: It simulates failure scenarios to test the resilience of Uber's distributed systems. 👉 Continuous Testing: Integrated into the deployment pipeline, it keeps resilience a focus throughout development. 👉 Seamless Integration: Chaos Engineering is embedded in Uber’s operations, enabling constant, real-world testing. 👉 Early Issue Detection: It helps identify and address vulnerabilities before they cause downtime. 👉 Industry Leadership: Uber sets a high standard for resilience, proving complex systems can be robust. 👉 Edge Case Preparedness: The platform ensures Uber is ready for edge cases that might disrupt operations. By making Chaos Engineering a core process, Uber reinforces trust, ensuring reliable service delivery, no matter what. Source- https://lnkd.in/gMyeMTJr #Uber #ChaosEngineering #ChaosAutomationPlatform #Scale #Reliability

Uber has unveiled a new approach to managing system loads called "Dynamic Load Shedding." This innovative technique aims to optimize performance and reduce costs by selectively shedding non-essential tasks during periods of high demand or system stress. By dynamically adjusting the workload based on real-time conditions, Uber seeks to maintain service reliability while maximizing efficiency. Below article explores the technical details behind this strategy and its potential implications for other organizations grappling with similar scalability challenges. https://lnkd.in/dBinyHnC

🚀 Transform Your Testing: Embrace Request Isolation! 🚀 Part 4 of our "Shifting Testing Left" series is out on TheNewStack! 🔍 Discover how request isolation can revolutionize your testing strategy. 🎯 Ensure highly accurate, interference-free tests in complex microservice environments. 🌐 Learn from industry leaders like Uber and DoorDash on how they achieve faster feedback and greater efficiency. ⚡️ Don't miss out on why you should shift left and empower your developers! 💻 Read full article here: https://hubs.li/Q02zHqWz0 #Microservices #DevOps #ShiftLeftTesting

Managing CI pipelines for a large monorepo can be challenging, especially at scale. Uber has developed strategies to keep their builds fast and efficient, even with 1,000 daily commits and over 50 million lines of code. In our upcoming webinar, we’ll cover Uber’s approach to optimizing CI/CD processes. We'll discuss: - Using Bazel to understand build targets and optimize CI processes - Dynamically generating CI build steps to handle complex changes efficiently - Improving CI performance through containerized environments - Custom tools Uber has built to ensure performant CI Join us on June 26 to learn how Uber handles CI for a large-scale monorepo. Register now to secure your spot and receive a recording of the event afterward: https://lnkd.in/eZBtuy2n

Choosing the right architecture can make or break the scalability and efficiency of your system! 💻 For example, Netflix scales its services independently using Microservices, allowing them to update features without downtime. Meanwhile, Uber uses an Event-Driven Architecture to process real-time updates, ensuring smooth rides for millions of users globally. Understanding the nuances of architectures like Monolithic, Serverless, or Event Sourcing can help you optimize performance and flexibility for your projects. 🚀 What's your go-to architecture for scaling success? Drop your thoughts below! 👇 #DidYouKnow #SoftwareArchitecture #Microservices #EventDriven #Serverless #TechTips #CloudComputing #Scalability #Innovation #DigitalTransformation #StarlingElevate #ElevateYourBusiness