Anshuman Khandelwal

How did we used Domain Driven Design  concept to break down our monolithic system into bounded contexts, and modernize it into cloud-based microservices? Also, how did we implement the bubble context architecture pattern? Read our Engineering Technical blog Credits : Danish Garg https://lnkd.in/dhPSDf4V

36

𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗱𝗼𝗶𝗻𝗴 𝘁𝗵𝗶𝗻𝗴𝘀 𝗿𝗶𝗴𝗵𝘁. 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗱𝗼𝗶𝗻𝗴 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝘁𝗵𝗶𝗻𝗴𝘀.  One of the major bottlenecks in scaling a true 𝗔𝗜 𝗔𝘂𝗴𝗺𝗲𝗻𝘁𝗲𝗱 𝗦𝗗𝗟𝗖 isn't model capability; it is the friction of context switching. Visual Studio Code 1.107 released on Dec 10 shifts the paradigm from 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝘁𝗼 𝗠𝘂𝗹𝘁𝗶-𝗔𝗴𝗲𝗻𝘁 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻.  With the new 𝗔𝗴𝗲𝗻𝘁 𝗛𝗤, we can move from "Pair Programming" to "Fleet Management," delegating work across a proper architectural hierarchy. 🤖 𝗧𝗵𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗿 (𝗟𝗼𝗰𝗮𝗹 𝗔𝗴𝗲𝗻𝘁): Your standard Copilot Chat. You use this for strategy, clarification, and quick answers. 🛠️ 𝗧𝗵𝗲 𝗪𝗼𝗿𝗸𝗲𝗿 (𝗟𝗼𝗰𝗮𝗹 𝗕𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗔𝗴𝗲𝗻𝘁): Deep work tasks delegated to run locally in isolated Git worktrees. They fix bugs and write tests in the background without blocking your editor or corrupting your current state.  ☁️ 𝗧𝗵𝗲 𝗦𝗰𝗮𝗹𝗲𝗿 (𝗖𝗹𝗼𝘂𝗱 𝗔𝗴𝗲𝗻𝘁): Heavy lifting (like documentation generation or security scanning) offloaded entirely to GitHub’s servers. This is grounded by the 𝗚𝗶𝘁𝗛𝘂𝗯 𝗠𝗖𝗣 𝗦𝗲𝗿𝘃𝗲𝗿, ensuring these agents share a unified context without hallucinating your project structure. For leaders, the value is clear: 𝗔𝘀𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗼𝘂𝘀 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻. We are no longer limited by the speed of a single chat interaction. This framework is extensible: you can engineer custom agents to handle your unique tech stack or deploy organization-wide agents to enforce architectural standards at scale. 𝗪𝗲 𝗮𝗿𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝗶𝗻𝗴 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘄𝗿𝗶𝘁𝗶𝗻𝗴 𝗰𝗼𝗱𝗲.   🚀 𝘚𝘵𝘰𝘱 𝘸𝘢𝘪𝘵𝘪𝘯𝘨. 𝘚𝘵𝘢𝘳𝘵 𝘥𝘦𝘭𝘦𝘨𝘢𝘵𝘪𝘯𝘨.  🏗️ 𝘉𝘶𝘪𝘭𝘥 𝘵𝘩𝘦 𝘧𝘢𝘤𝘵𝘰𝘳𝘺, 𝘯𝘰𝘵 𝘫𝘶𝘴𝘵 𝘵𝘩𝘦 𝘸𝘪𝘥𝘨𝘦𝘵.  ⚙️ 𝘐𝘯𝘯𝘰𝘷𝘢𝘵𝘪𝘰𝘯 𝘪𝘴 𝘢𝘯 𝘦𝘹𝘦𝘤𝘶𝘵𝘪𝘰𝘯 𝘱𝘳𝘰𝘣𝘭𝘦𝘮. 𝘛𝘩𝘪𝘴 𝘵𝘰𝘰𝘭𝘴𝘦𝘵 𝘨𝘪𝘷𝘦𝘴 𝘶𝘴 𝘵𝘩𝘦 𝘥𝘪𝘴𝘤𝘪𝘱𝘭𝘪𝘯𝘦 𝘵𝘰 𝘦𝘹𝘦𝘤𝘶𝘵𝘦 𝘪𝘯 𝘱𝘢𝘳𝘢𝘭𝘭𝘦𝘭. https://lnkd.in/gGYcRjD4

28

1 Comment

🚀 Most production issues aren’t caused by bad code, they’re caused by bad app design. If you’re building applications for the cloud, containers, or microservices, the 12-Factor App is still one of the most practical playbooks out there. Why it matters 👇 ✅ Predictable deployments ✅ Easy scaling ✅ Cleaner config management ✅ Fewer “works on my machine” problems From stateless processes to environment-based configuration, these principles help teams move faster with confidence in production. 📖 I wrote a clear, practical breakdown here on Medium: 👉 https://lnkd.in/ePaNAeBj 💬 Which of the 12 factors do you find hardest to follow in real projects? #12FactorApp #CloudNative #DevOps #SoftwareEngineering #Microservices #BackendDevelopment #ScalableSystems

11

1 Comment

👨‍💻 Indian IT Services: facing Ctrl+Alt+AI in our own backyard! 🤔 💰 Valuations of India’s IT giants (TCS, Infosys, HCL Tech, etc.) have slipped ~24% since Jan 2025 📉 as AI disruption, slowing client demand, and U.S. tariff jitters rattle investors. 📅 April–June growth? A sluggish ~1.5%, the weakest in 4 years. FPIs are selling, layoffs are rising, and the once-unshakable services model is looking…shaky. FT Report 👉 https://lnkd.in/gDKM9_E6 💰 Meanwhile, the mid-tier challengers are sprinting ahead — clocking ~20% revenue growth 🚀 thanks to AI efficiencies and sharper execution. ET Coverage 👉 https://lnkd.in/gcxgmXXp But here’s the real twist: 🖥️ AI isn’t the only “culprit” … Global Capability Centers (GCCs) are quietly eating into India’s IT services pie. Multinationals are moving work in-house, and by 2026, 120+ new GCCs are set to open in India alone. TOI Insight 👉 https://lnkd.in/gFp6Bbpx 💡 Where do we go from here? This isn’t a doom story. It’s a reboot opportunity. From resource outsourcing ➝ to outcome orchestration From headcount-led growth ➝ to outcome-led value From reacting to GCCs ➝ to co-creating with them Agility is now the superpower 🦸 — and reinvention is the only strategy that works. Because disruption doesn’t destroy those who pivot — it rewards them. Can Indian IT reinvent its Ctrl+Alt+AI moment into Ctrl+Alt+Grow? I hope so. The world is watching. 🌍 #India #ITServices #AI #GCC #Reinvention #TechTransformation #CtrlAltAI

26

1 Comment

Excited to speak at Kubernetes Community Day (KCD) New York | June 4, 2025 along with Vijay Kumar Soni. Running critical financial services and payments workloads in a hybrid cloud environment presents unique challenges, requiring careful planning and execution. This involves managing diverse environments, ensuring compliance, and optimizing costs while maintaining security and performance. In this talk, we'll share real-world challenges, practical solutions, and lessons learned when running critical workload in Hybrid Cloud environment within financial services and payments domain. #KCDNewYork #CNCF #HybridCloud #Discover #CapitalOne #LinuxFoundation #CloudNative #Kubernetes #Payments #FinTech Discover Discover Network Capital One Cloud Native Computing Foundation (CNCF) The Linux Foundation Olga Zhornitsky

32

Very Interesting perspectives, I may disagree with a few and align with Many of the views shared, interesting views, perspectives, and practices nevertheless !! 1. The Counterintuitive Truth: Code Quality Does Not Equal Product Success Prasanna’s most striking lesson for engineers is that there is no direct relationship between high code quality and building a successful product. While technical excellence is a worthy goal, it is not the end goal. The ultimate measure of success is whether you are solving a real problem for people. < I am on the Edge with this one. While I am a strong proponent of Quality output/outcome, the ultimate measure of success is, however, the real problem solved :) Ramanan Natarajan - Would love to hear your thoughts on this :) 2. The Real Productivity Engine: Structure as the Foundation for Tools While Block is gaining attention for its powerful internal AI agent, Goose, Prasanna reveals that the single most impactful change for boosting productivity wasn't a tool, but a fundamental organizational restructure. The company shifted from a siloed structure to a unified, functional one. This new functional structure unlocked three primary benefits: > It created a singular focus on technology and technical excellence across the entire organization. > It allowed leaders to drive forward AI and platform depth for the whole company, rather than in isolated pockets. > It changed the hiring mindset. Instead of treating engineers as a "commodity" to be added to a business unit to increase feature output, "mythical man month", the focus shifted to building common platforms and leveraging deep experts across the entire organization. This unified structure not only drove technical depth but also created the ideal environment for small-scale experiments to be identified, supported, and scaled across the company, rather than dying within a business unit silo. < It's not always the Tool, it's the Mindset !! 3. The Principle of Momentum: Start Small to Win Big: The most successful and durable innovations rarely begin as massive, top-down corporate initiatives. Instead, they grow from small, focused experiments. < "Start small with everything." 4. The Human Element: Hire for a "Learning Mindset": The company now optimizes for a "learning mindset." They are less concerned with finding "amazing AI practitioners on the get-go." Instead, they prioritize finding people from recent college graduates to industry veterans who are eager, open to learning, and willing to embrace new tools. < Meta cognition is undervalued !! #organisationCluture #AI #Productivity https://lnkd.in/gw6saKXp

11

Grateful to The Better India for featuring Xcelevate Skills Foundation and bringing this story to a wider audience. This recognition is important not for us, but for the problem it highlights. India produces millions of graduates every year, yet a significant percentage struggle to find meaningful employment. Among them, a large number are first-generation and underserved youth who never even get a fair chance to be evaluated beyond their degrees. At Xcelevate, we are trying to solve exactly that. Through our residential Gurukul model in Chennai, we work with high-potential youth from underserved backgrounds not just to train them, but to prepare them for real careers in corporate environments. The idea is simple: talent is everywhere, it just needs the right structure, mentorship, and opportunity to be unlocked What we are seeing reinforces this belief: Strong performance in demanding corporate roles High retention Growing confidence and ownership This is still a small step relative to the scale of the problem. But it is a start. Thank you again to The Better India for telling this story. 👉 Read more: https://lnkd.in/gdXuGTwG

36

6 Comments

𝐖𝐡𝐲 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 𝐒𝐡𝐨𝐮𝐥𝐝 𝐓𝐡𝐢𝐧𝐤 𝐋𝐢𝐤𝐞 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐋𝐞𝐚𝐝𝐞𝐫𝐬 In today’s digital landscape, the role of an architect goes far beyond designing systems. To truly drive impact, architects must think and operate like product leaders. Great architecture isn’t just technically sound. It is purposeful, customer centric, and aligned with business outcomes. And that mindset comes from product thinking. 𝐇𝐞𝐫𝐞’𝐬 𝐰𝐡𝐲 𝐭𝐡𝐢𝐬 𝐬𝐡𝐢𝐟𝐭 𝐦𝐚𝐭𝐭𝐞𝐫𝐬: 🔹 Customer value comes first Architecture decisions should enable faster, simpler, and more reliable experiences for customers not just elegant designs. 🔹 Prioritizations becomes sharper Product leaders know how to balance ambition with practicality. Architects benefit from the same discipline building what matters most at the right time. 🔹 Trade-offs become strategic, not reactive Every decision has a cost. Thinking like a product leader ensures those trade-offs support long term value, not just short-term delivery. 🔹 Alignment across teams becomes easier When architects speak in business outcomes, not only technical terms, it bridges engineering, product, and leadership seamlessly. 🔹 Innovation becomes intentional Product thinking encourages experimentation, learning, and continuous refinement qualities essential to modern architecture. Today’s most effective architects don’t just design systems. They shape vision, influence strategy, and connect technology with measurable outcomes. Architecture is a technical discipline. But the mindset behind it is deeply product-driven. #SolutionArchitecture #ProductThinking #TechLeadership #EnterpriseArchitecture #DigitalStrategy #ArchitectureMindset #EngineeringExcellence #BusinessAlignment #InnovationLeadership

11

As of this week, Hexaware Technologies has unveiled "Zero License," an Agentic AI tool designed to replace bloated SaaS workflows with AI. The trend is clear: Enterprise AI is evolving towards AI-driven execution to tackle the "execution problem" rather than merely addressing the "tooling problem." Implications for the IT industry include: 1. Shorter Implementation: Transitioning from years to months. 2. Lower Costs: Replacing per-user software licenses with AI Agents. 3. Higher Efficiency: AI serving as the primary execution layer. The shift to Agentic AI is accelerating faster than anticipated, with enterprise adoption transitioning from experimentation to necessity.

24