Ujjawal Tyagi
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
🌐 dev.toSource
From Dev.to - cicd: AWS Deployment Pipeline for Indian Startups: Our GitHub Actions + ECS Fargate Setup
🌐 dev.toSource
At Xenotix Labs (https://www.xenotixlabs.com), we've shipped 30+ production apps in 4 years across D2C, edtech, fintech, healthtech, SaaS, and marketplaces. Every single one followed the same playbook. Flutter for mobile (iOS + Android in one codebase) Next.js for web (SSR for SE
🌐 dev.toSource
Every Flutter team has the same broken ritual. The designer finishes a beautiful Figma file. The developer opens it, stares at a spacing value of "14.3px", sighs, and rebuilds the UI from scratch. Three weeks later, the product ships with colors and paddings that don't match the
🌐 dev.toSource
Most engineering blogs that talk about Kafka either quote the Netflix case study or walk you through the "hello world" producer-consumer example. Both are useless if you're actually trying to decide whether to adopt Kafka for a product that might hit a million users — or stay at
🌐 dev.toSource
Insurance in India runs on surveys. When a claim comes in—a car accident, a flooded basement, a health emergency—a surveyor physically visits the site, inspects the damage, documents it with photos and reports, and submits the assessment back to the insurer. The turnaround used t
🌐 dev.toSource
Every team I've talked to that adopted microservices in the last five years has the same arc: enthusiasm at month one, regret at month nine, sober refactoring at month eighteen. At Xenotix Labs we've shipped 30+ platforms on microservices, and we've made every one of these mistak
🌐 dev.toSource
Message queues are one of those architectural choices where the wrong pick haunts you for years. Pick Kafka when RabbitMQ would have done, and you've bought a 3-node cluster, ZooKeeper (or KRaft) operations, partition management, and consumer group coordination — all to replace w
🌐 dev.toSource
Every Indian founder I've met in the last two years has the same WhatsApp problem. Customers DM them at all hours. Half the queries are the same five questions. The founder ends up being the company's unpaid, always-on customer support. At 50 customers a day it's manageable. At 5
🌐 dev.toSource
webdev, architecture, node, kafkaIndia consumes cricket like no other country on earth. When Kohli walks out to bat, millions of users hit refresh simultaneously. When a wicket falls, chat rooms explode. When an opinion-trading market opens on the next ball, orders pour in at rat