<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Backend on Prateek Sharma</title>
		<link>https://prateeksharma.me/categories/backend/</link>
		<description>Recent content in Backend on Prateek Sharma</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://prateeksharma.me/categories/backend/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Endpoint maps over hand-rolled methods</title>
				<link>https://prateeksharma.me/blog/endpoint-maps-over-hand-rolled-methods/</link>
				<pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/blog/endpoint-maps-over-hand-rolled-methods/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve now written two client libraries for the same exchange API — one in&#xA;&lt;a href=&#34;https://prateeksharma.me/projects/wazirx-connector-go/&#34;&gt;Go&lt;/a&gt;&#xA;, one in&#xA;&lt;a href=&#34;https://prateeksharma.me/projects/wazirx-connector-java/&#34;&gt;Java&lt;/a&gt;&#xA; — and the thing I&amp;rsquo;d keep from both is&#xA;the same: don&amp;rsquo;t write a method per endpoint. Describe the endpoints as data and&#xA;dispatch through one function.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-shape-of-the-problem&#34;&gt;The shape of the problem&lt;/h2&gt;&#xA;&lt;p&gt;The API has roughly two dozen endpoints. They differ in four ways:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;HTTP verb (&lt;code&gt;GET&lt;/code&gt;, &lt;code&gt;POST&lt;/code&gt;, &lt;code&gt;DELETE&lt;/code&gt;)&lt;/li&gt;&#xA;&lt;li&gt;path&lt;/li&gt;&#xA;&lt;li&gt;whether the request must be signed&lt;/li&gt;&#xA;&lt;li&gt;the response body&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Everything else — building query params, adding a signature, choosing the verb&#xA;handler, parsing the response — is identical. Writing a hand-rolled method per&#xA;endpoint means writing that identical body 25 times, and then maintaining 25&#xA;copies of it when the signing scheme or the base URL handling changes.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Tidylnk</title>
				<link>https://prateeksharma.me/projects/tidylnk/</link>
				<pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/projects/tidylnk/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://admin.tidylnk.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Tidylnk&lt;/a&gt;&#xA; is a URL shortener I built to have a&#xA;simple, self-hosted alternative to the usual third-party link shorteners, with an&#xA;admin panel to manage and track links.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tech-stack&#34;&gt;Tech stack&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Backend&lt;/strong&gt; — Go, serving the redirect and link-management APIs.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Frontend&lt;/strong&gt; — a React admin panel for creating, organizing, and tracking&#xA;shortened links.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt; — PostgreSQL as the primary datastore for link records, with Redis&#xA;on the redirect hot path for fast lookups.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Deployment&lt;/strong&gt; — backend and database containerized with Docker and deployed on&#xA;Railway.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;why-i-built-it&#34;&gt;Why I built it&lt;/h2&gt;&#xA;&lt;p&gt;I wanted a link shortener I fully controlled — no reliance on a third party&amp;rsquo;s&#xA;uptime, rate limits, or analytics restrictions — and a project to exercise Go and&#xA;Redis together on a workload where caching genuinely matters: redirect latency.&lt;/p&gt;</description>
			</item>
			<item>
				<title>WazirX Go Connector</title>
				<link>https://prateeksharma.me/projects/wazirx-connector-go/</link>
				<pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/projects/wazirx-connector-go/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://wazirx.com&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;WazirX&lt;/a&gt;&#xA; is one of India&amp;rsquo;s largest crypto exchanges, and&#xA;while its REST API is well documented, it doesn&amp;rsquo;t ship an official Go client. I&#xA;wanted to poke at their API for a side project and didn&amp;rsquo;t want to hand-roll&#xA;request signing and endpoint plumbing every time, so I built&#xA;&lt;a href=&#34;https://github.com/pratts/wazirx-connector-go&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;wazirx-connector-go&lt;/a&gt;&#xA; and&#xA;open-sourced it once it was in decent shape.&lt;/p&gt;&#xA;&lt;h2 id=&#34;avoiding-25-near-identical-methods&#34;&gt;Avoiding ~25 near-identical methods&lt;/h2&gt;&#xA;&lt;p&gt;The exchange exposes close to two dozen endpoints — tickers, order book depth,&#xA;order placement, withdrawals, sub-account transfers, and so on. Writing a&#xA;hand-rolled method for each one would have meant the same boilerplate repeated&#xA;two dozen times: build params, sign if needed, pick GET/POST/DELETE, hit the URL,&#xA;parse the response.&lt;/p&gt;</description>
			</item>
			<item>
				<title>WazirX Java Connector</title>
				<link>https://prateeksharma.me/projects/wazirx-connector-java/</link>
				<pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/projects/wazirx-connector-java/</guid>
				<description>&lt;p&gt;After building the &lt;a href=&#34;https://prateeksharma.me/projects/wazirx-connector-go/&#34;&gt;Go connector&lt;/a&gt;&#xA; for WazirX, I&#xA;wanted the same thing on the JVM — but WazirX doesn&amp;rsquo;t publish an official Java&#xA;client at all, REST or WebSocket. The REST half was a fairly direct port of what&#xA;I&amp;rsquo;d already learned building the Go client. The WebSocket half turned out to be&#xA;its own project.&lt;/p&gt;&#xA;&lt;h2 id=&#34;letting-callers-choose-their-failure-granularity&#34;&gt;Letting callers choose their failure granularity&lt;/h2&gt;&#xA;&lt;p&gt;For errors, I didn&amp;rsquo;t want every caller forced into one giant catch-all&#xA;exception, but I also didn&amp;rsquo;t want to force a &lt;code&gt;try/catch&lt;/code&gt; at every single call&#xA;site. I split errors into two, with one extending the other:&lt;/p&gt;</description>
			</item>
			<item>
				<title>CoinTracker</title>
				<link>https://prateeksharma.me/experience/cointracker/</link>
				<pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/experience/cointracker/</guid>
				<description>&lt;p&gt;CoinTracker is a crypto portfolio and tax platform. I worked on the ingestion&#xA;and reconciliation side: getting on-chain data into the system correctly, and&#xA;keeping wallet balances consistent across chains.&lt;/p&gt;&#xA;&lt;h2 id=&#34;engineering-areas&#34;&gt;Engineering areas&lt;/h2&gt;&#xA;&lt;h3 id=&#34;blockchain-integrations&#34;&gt;Blockchain integrations&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Integrated &lt;strong&gt;Cardano&lt;/strong&gt; and &lt;strong&gt;Stellar&lt;/strong&gt;, reading on-chain data from Snowflake&#xA;for balance reconciliation, transaction parsing, and portfolio tracking.&lt;/li&gt;&#xA;&lt;li&gt;Onboarded &lt;strong&gt;Akash&lt;/strong&gt; and &lt;strong&gt;Axelar&lt;/strong&gt; (cross-chain), plus &lt;strong&gt;Bitcoin Ordinals,&#xA;Inscriptions, BRC-20, and Runes&lt;/strong&gt; via the Ordiscan API.&lt;/li&gt;&#xA;&lt;li&gt;Worked behind a unified blockchain abstraction so each new chain was a smaller,&#xA;more predictable piece of work than the last.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fault-tolerant-wallet-sync&#34;&gt;Fault-tolerant wallet sync&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Wrote the business logic behind &lt;strong&gt;Temporal&lt;/strong&gt; workers for wallet-sync&#xA;workflows: idempotent, retry-safe, and consistent across chains.&lt;/li&gt;&#xA;&lt;li&gt;Built reconciliation pipelines and validation checks so cross-chain data&#xA;disagreements surface as failures rather than silently wrong balances.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;data-tooling&#34;&gt;Data tooling&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Built and consumed &lt;strong&gt;Flask&lt;/strong&gt; REST APIs and CLI scripts for ingestion,&#xA;validation, and reconciliation.&lt;/li&gt;&#xA;&lt;li&gt;Used &lt;strong&gt;pytest&lt;/strong&gt; and &lt;strong&gt;mypy&lt;/strong&gt; to keep correctness and type safety enforced in&#xA;CI.&lt;/li&gt;&#xA;&lt;li&gt;Adopted Claude Code as an agentic assistant for feature work, debugging, and&#xA;issue resolution.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stack&#34;&gt;Stack&lt;/h2&gt;&#xA;&lt;p&gt;Python · Flask · Temporal · Snowflake · pytest · mypy&lt;/p&gt;</description>
			</item>
			<item>
				<title>Emission Critical</title>
				<link>https://prateeksharma.me/experience/emission-critical/</link>
				<pubDate>Sun, 01 May 2022 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/experience/emission-critical/</guid>
				<description>&lt;p&gt;Emission Critical is a B2B SaaS platform for enterprise carbon footprint and&#xA;sustainability tracking. I led the backend: the data model, the APIs, and the&#xA;computation engine.&lt;/p&gt;&#xA;&lt;h2 id=&#34;engineering-areas&#34;&gt;Engineering areas&lt;/h2&gt;&#xA;&lt;h3 id=&#34;multi-tenant-platform&#34;&gt;Multi-tenant platform&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Architected a &lt;strong&gt;multi-tenant PostgreSQL schema&lt;/strong&gt; with tenant-level data&#xA;isolation.&lt;/li&gt;&#xA;&lt;li&gt;Integrated &lt;strong&gt;Auth0&lt;/strong&gt; for identity and multi-tenant RBAC.&lt;/li&gt;&#xA;&lt;li&gt;Streamlined data ingestion through Excel parsing and automated &lt;strong&gt;AWS S3&lt;/strong&gt;&#xA;pipelines.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;carbon-accounting-engine&#34;&gt;Carbon accounting engine&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Designed the engine for full &lt;strong&gt;Scope 1, 2, and 3&lt;/strong&gt; emissions tracking and&#xA;product carbon footprints.&lt;/li&gt;&#xA;&lt;li&gt;Cut computation latency ~50% and improved throughput a further ~30% with&#xA;better indexing and batch processing.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;search-and-lookups&#34;&gt;Search and lookups&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Built parsers and &lt;strong&gt;Meilisearch&lt;/strong&gt;-backed full-text search over public emission&#xA;factor databases.&lt;/li&gt;&#xA;&lt;li&gt;Exposed REST APIs for emission-factor lookups feeding downstream carbon&#xA;computation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;observability&#34;&gt;Observability&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Stood up observability with &lt;strong&gt;OpenTelemetry&lt;/strong&gt;, SigNoz, and Kubernetes-native&#xA;logging for real-time diagnostics.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stack&#34;&gt;Stack&lt;/h2&gt;&#xA;&lt;p&gt;NestJS · TypeScript · PostgreSQL · Auth0 · Meilisearch · AWS · Kubernetes ·&#xA;OpenTelemetry&lt;/p&gt;</description>
			</item>
			<item>
				<title>Mind Sports League</title>
				<link>https://prateeksharma.me/experience/mind-sports-league/</link>
				<pubDate>Mon, 01 Mar 2021 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/experience/mind-sports-league/</guid>
				<description>&lt;p&gt;Mind Sports League ran an online poker platform. I led development of the game&#xA;and tournament features on top of the existing platform.&lt;/p&gt;&#xA;&lt;h2 id=&#34;engineering-areas&#34;&gt;Engineering areas&lt;/h2&gt;&#xA;&lt;h3 id=&#34;tournament-features&#34;&gt;Tournament features&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Built advanced tournament mechanics: &lt;strong&gt;hand-for-hand&lt;/strong&gt; play, &lt;strong&gt;re-entry&lt;/strong&gt;, and&#xA;&lt;strong&gt;table balancing&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;real-time-backend&#34;&gt;Real-time backend&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Engineered game-state management and an &lt;strong&gt;event-driven backend&lt;/strong&gt; handling&#xA;thousands of concurrent players with low-latency communication.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;training-tools&#34;&gt;Training tools&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Built a &lt;strong&gt;poker simulator&lt;/strong&gt; integrated with an educational platform, so&#xA;players could practise strategy and review analytics.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stack&#34;&gt;Stack&lt;/h2&gt;&#xA;&lt;p&gt;Real-time / event-driven backend · game-state management · AngularJS (simulator)&lt;/p&gt;</description>
			</item>
			<item>
				<title>Yolobus</title>
				<link>https://prateeksharma.me/experience/yolobus/</link>
				<pubDate>Sun, 01 Mar 2020 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/experience/yolobus/</guid>
				<description>&lt;p&gt;Yolobus operated intercity buses. I worked on the in-house systems for inventory&#xA;and bookings.&lt;/p&gt;&#xA;&lt;h2 id=&#34;engineering-areas&#34;&gt;Engineering areas&lt;/h2&gt;&#xA;&lt;h3 id=&#34;global-distribution-system&#34;&gt;Global Distribution System&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Designed the &lt;strong&gt;database architecture&lt;/strong&gt; for an in-house GDS managing trip&#xA;inventory and real-time bookings.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;booking-engine&#34;&gt;Booking engine&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Migrated core services to &lt;strong&gt;Python / Django&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Built a &lt;strong&gt;serverless ticket-booking engine&lt;/strong&gt; on &lt;strong&gt;AWS Chalice&lt;/strong&gt;, improving&#xA;maintainability and transaction scalability.&lt;/li&gt;&#xA;&lt;li&gt;Implemented high-throughput booking APIs integrating third-party payment and&#xA;inventory providers (e.g. Redbus, Paytm).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stack&#34;&gt;Stack&lt;/h2&gt;&#xA;&lt;p&gt;Python · Django · AWS Chalice · PostgreSQL · REST APIs&lt;/p&gt;</description>
			</item>
			<item>
				<title>Adda52 — Delta Corp</title>
				<link>https://prateeksharma.me/experience/adda52/</link>
				<pubDate>Mon, 01 Sep 2014 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/experience/adda52/</guid>
				<description>&lt;p&gt;Adda52 is one of India&amp;rsquo;s largest real-money poker platforms. I joined as a&#xA;graduate trainee in 2014 and left in 2020 as a Senior Software Engineer, working&#xA;across the game backend, load and resilience testing, and the public platform.&lt;/p&gt;&#xA;&lt;h2 id=&#34;role-progression&#34;&gt;Role progression&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Graduate Engineer Trainee&lt;/strong&gt; (Sep 2014 – Oct 2015)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Software Engineer&lt;/strong&gt; (Oct 2015 – Oct 2016)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Senior Software Engineer&lt;/strong&gt; (Oct 2016 – Feb 2020)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;engineering-areas&#34;&gt;Engineering areas&lt;/h2&gt;&#xA;&lt;h3 id=&#34;game-logic&#34;&gt;Game logic&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Contributed to core poker cash-game and tournament-management modules.&lt;/li&gt;&#xA;&lt;li&gt;Implemented the &lt;strong&gt;OFC&lt;/strong&gt; poker variant end to end on the &lt;code&gt;adda52live.com&lt;/code&gt;&#xA;frontend (Angular 2).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;load-and-resilience-testing&#34;&gt;Load and resilience testing&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Enhanced Java-based user-behaviour simulators to &lt;strong&gt;load test real-time poker&#xA;servers at 10,000+ concurrent users&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Built &lt;strong&gt;disaster-recovery systems&lt;/strong&gt; for zero-downtime gameplay — restoring&#xA;poker games and player state after a failure.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;platform-migration&#34;&gt;Platform migration&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Led migration of the public gaming platform from &lt;strong&gt;PHP to Node.js&lt;/strong&gt;, improving&#xA;performance and maintainability.&lt;/li&gt;&#xA;&lt;li&gt;Built Angular 2 interfaces for event bookings on &lt;code&gt;adda52live.com&lt;/code&gt; and&#xA;user-segmentation logic for targeted marketing.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;delivery&#34;&gt;Delivery&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Developed Gradle-based CI/CD pipelines with &lt;strong&gt;Jenkins&lt;/strong&gt;, automating builds and&#xA;reducing integration friction.&lt;/li&gt;&#xA;&lt;li&gt;Represented a 6-member team in sprint planning and stakeholder meetings,&#xA;coordinating with QA, product, and DevOps.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stack&#34;&gt;Stack&lt;/h2&gt;&#xA;&lt;p&gt;Java · Node.js · Angular 2 · Jenkins · Gradle&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
