{ "version": 5, "publishedAt": "2026-08-31T17:52:38.711423501Z", "summary": { "domain": "sat0ru.dev", "imageSubText": "Delhi, India · Remote-friendly", "heroHighlightText": "Open to backend roles", "heroName": "Samarth Negi", "heroSubText": "Backend engineer · distributed systems", "heroDetails": "I build high-throughput backend systems in Go and Python. Most recently cut API p99 latency by 60% for a platform serving 2M daily users at Finlay.", "updatedAt": "2026-08-31T23:22:36.099054+05:30" }, "projects": [ { "id": "seed-project-1", "title": "Brocode Crypto Exchange", "slug": "brocode-crypto-exchange", "description": "Centralized Cryptocoin Exchange supporting spots \u0026 perpetuals.", "stack": [ "Golang", "Kafka", "kubernetes", "Postgres" ], "github": "https://github.com/Sam-Frost/Brocode-Exchange-Backend", "liveLink": "https://exchange.sat0ru.dev", "visible": true, "order": 0, "updatedAt": "2026-08-31T20:16:45.622922+05:30" }, { "id": "seed-project-2", "title": "Coding Agent", "slug": "coding-agent", "description": "Double-entry accounting API for fintech startups. Sub-10ms reads.", "stack": [ "Golang", "Sqlite" ], "github": "https://github.com/Sam-Frost/Brocode-cli", "liveLink": "https://codex.sat0ru.dev", "visible": true, "order": 1, "updatedAt": "2026-08-31T20:16:45.622922+05:30" }, { "id": "seed-project-3", "title": "Shadow-Link", "slug": "shadow-link", "description": "Custom VPN built in golang. To be done is doneee\n", "stack": [ "Golang" ], "github": "https://github.com/Sam-Frost/Shadow-Link", "liveLink": "https://shadowLink.sat0ru.dev", "visible": true, "order": 2, "updatedAt": "2026-08-31T20:35:42.984074+05:30" }, { "id": "seed-project-4", "title": "BastionX", "slug": "bastionx", "description": "Custom SSH implementation in golang.", "stack": [ "Golang" ], "github": "https://github.com/Sam-Frost/BastionX", "liveLink": "https://bastionx.sat0ru.dev", "visible": true, "order": 3, "updatedAt": "2026-08-31T20:16:45.622922+05:30" } ], "experiences": [ { "id": "seed-exp-1", "logo": "SL", "position": "Software Engineer", "company": "Saralya Tech Pvt. Ltd", "description": "Built multi tenant LMS system from ground up, making lending easy for NBFCs", "details": [ "Handled DLT registration \u0026 setup, API Integration and mananing multi tentat DLT system with automated fallbacks" ], "techStack": [ "TypeScript", "NestJs", "PostgreSQL", "Redis", "Docker" ], "startDate": "June 2026", "endDate": "Present", "visible": true, "order": 0, "updatedAt": "2026-08-31T20:16:45.622922+05:30" }, { "id": "seed-exp-2", "logo": "BT", "position": "Associate Software Engineer", "company": "BitxiaTech Pvt. Ltd.", "description": "Built scalable Spring Boot backend services for agriculture/eNAM systems with Kafka-based asynchronous communication, high availability patterns, and optimized database performance.", "details": [ "Developed and scaled 3 core services using Kafka-based asynchronous inter-service communication.", "Implemented ONDC protocol for agriculture services, enabling interoperability between buyers, sellers, and logistics providers.", "Achieved 99.9% availability by implementing Retry and Circuit Breaker patterns to prevent cascading failures.", "Cut API latency by 30% using caching and SQL query plan analysis.", "Designed scalable database schemas supporting 1M+ rows while keeping query execution under 50ms.", "Reduced deployment time by 60% using Docker, Kubernetes, and CI/CD layer caching." ], "techStack": [ "Java", "Spring Boot", "Kafka", "PostgreSQL", "Redis", "Docker", "Kubernetes" ], "startDate": "Feb 2025", "endDate": "Oct 2025", "visible": true, "order": 1, "updatedAt": "2026-08-31T20:16:45.622922+05:30" }, { "id": "seed-exp-3", "logo": "TH", "position": "Backend Developer", "company": "Techostinger India Pvt. Ltd.", "description": "Owned backend development for production APIs, real-time chat, media processing pipelines, payments, and automated deployment workflows.", "details": [ "Designed and developed RESTful APIs and GitLab CI pipelines for automated deployment.", "Engineered a real-time chat system using WebSocket and Redis supporting 1,000+ concurrent connections.", "Reduced database writes by 70% for real-time last-seen user activity tracking.", "Built an asynchronous media pipeline using AWS S3 and SQS, reducing main-thread load by 80%.", "Wrote 150+ unit and integration tests with Vitest and Supertest, reaching 80% code coverage.", "Integrated Stripe for secure transactions and subscription payments." ], "techStack": [ "Node.js", "Express", "TypeScript", "Redis", "WebSocket", "AWS S3", "AWS SQS", "Stripe" ], "startDate": "June 2024", "endDate": "Dec 2024", "visible": true, "order": 2, "updatedAt": "2026-08-31T20:16:45.622922+05:30" }, { "id": "seed-exp-4", "logo": "JM", "position": "Mobile Development Intern", "company": "JMVL", "description": "Built a cross-platform Flutter application with API integrations, authentication flows, and stable state management for Android and iOS.", "details": [ "Developed a cross-platform mobile application using Flutter for Android and iOS.", "Integrated 15+ REST APIs for real-time data handling, authentication, and core app functionality.", "Implemented Bloc and Provider state management, reducing memory leaks and improving app stability by 20%." ], "techStack": [ "Flutter", "Dart", "REST APIs", "Bloc", "Provider" ], "startDate": "June 2023", "endDate": "Dec 2023", "visible": true, "order": 3, "updatedAt": "2026-08-31T20:16:45.622922+05:30" } ], "blogs": [ { "id": "seed-blog-1", "title": "Image bluring at client vs server", "slug": "image-bluring-at-client-vs-server", "readTime": "5 min read", "genre": "Backend", "date": "Dec 2024", "body": "# Image Blurring at Client vs Server\n\nI was building a matrimonial platform when I came across this issue of image blurring. We needed to make sure the images of the users are blurred before they hit the client in order to maintain privacy of the user.\n\nI encountered this again while browsing LinkedIn. I noticed that the \"Viewers you might be interested in\" section had images blurred from the backend, likely because it's a paid feature. If users could access the data just by inspecting elements, it wouldn't be much of a paywall. In contrast, the \"People you may know\" section applied the blur effect on the client side, making it easy to reveal image URLs by tinkering with the inspect element.\n\nThis experience led me to explore the differences between client-side and server-side blurring.\n\n## Client Side Blurring\n\nClient-side blurring is the process of blurring the image on the client's machine using CSS or JavaScript running on the browser.\n\nThe key advantage of client-side blurring is offloading the processing from the server. While blurring may seem lightweight initially, at scale, handling thousands of simultaneous requests can create significant computational overhead.\n\n## Server Side Blurring\n\nServer-side blurring involves processing the image on the server before sending it to the client.\n\nAnother approach is to generate and store two versions of the image at the time of upload, allowing the system to serve the appropriate version as needed. This approach is more efficient than the previous one since the image is blurred only once and stored, allowing us to serve the pre-processed version directly to the client. This reduces computational overhead and minimizes latency whenever the client requests the image.\n\n## Why Prefer Server Side Blurring\n\n- Client-side blurring is limited to CSS and JavaScript, while server-side processing allows the use of custom libraries and different programming languages.\n- Server-side blurring offers more control over image modifications, enabling advanced processing beyond just blurring.\n\n## Conclusion\n\nImage blurring can be a computationally expensive task. It is preferred to offload this computationally expensive task to the client whenever possible.\n\nOf course, not everything can be offloaded to the client. If there is sensitive information (for example, people who have viewed your profile on LinkedIn) which shall not be accessible to the user or is hidden behind a paywall, that blurring must happen server-side.\n\nSo the general approach would be to offload blurring tasks as much as we can to the client, but whenever we have to deal with sensitive information, the server has to bear the extra computational cost of blurring.\n", "visible": true, "order": 0, "updatedAt": "2026-08-31T20:16:45.622922+05:30" } ] }