Third-year CSE student building a suite of six interconnected services with FastAPI, PostgreSQL, Redis, and Apache Airflow — designed as one system, not six separate projects, with CI/CD via GitHub Actions on every service.
These aren't six standalone projects — they're designed to depend on each other, the way production systems do. Click a node to jump to its entry in the service registry below.
All under active development. Each entry below is what's actually implemented — expand for the technical detail.
Redis as the hot-path cache for O(1) redirect lookups, PostgreSQL as source of truth for link metadata and click events — separating read-latency from write-durability concerns.StreamPulse, driving real-time analytics without direct service coupling.WorkerMesh for inter-service authentication.WorkerMesh via task queue — keeps the payment API non-blocking.AuthCore, receives post-payment jobs dispatched by PayBridge — completing the coordination chain.LinkForge's click-event channel, broadcasting live analytics updates — closes the loop from link creation to live reporting.What every service in the registry above is actually built with.
I'm Aditya Bhattacharjee, a second-year B.Tech CSE student at SRM Institute of Science and Technology, specializing in backend systems, REST APIs, and data pipeline engineering. I'm building the six-service system above as one interconnected whole rather than isolated coursework projects — with performance, reliability, and observability treated as first-class requirements, not afterthoughts. I work comfortably independently in remote environments and practice CI/CD-first development with GitHub Actions on every service.
Reach out about internships, collaboration, or the system above — happy to walk through any part of it.