Welcome to my digital workspace! I'm a full-stack developer specializing in Next.js, FastAPI, and cloud-native AWS deployments. This portfolio explores my recent work—from building internal automated sales tools that integrate complex logistics APIs to launching custom software packages that scale fast. Check out the live projects and let me know what you think!
No reviews yetBe the first to leave a review for Personal Portfolio-Manas Bhatia
Maker
📌
Hi Product Hunt! 👋
I’m excited to launch manasbhatia.me today. As someone balancing an EE degree with a role as a SDE, I wanted a clean, fast space to document my development journey.
My focus lately has been on cloud-native deployments (AWS EC2/S3/CloudFront), API integrations for billing and logistics, and speeding up development cycles with Next.js. And making full stack web and mobile applications using NextJs, FastAPI and React Native.
I’d love your feedback on the site’s performance, design, or any of the open-source projects listed. I'll be hanging out in the comments all day to answer questions!
Report
Curious how you handle the logistics API integrations on the backend, are you wrapping FastAPI around them directly or building some kind of adapter layer to deal with rate limits and schema differences?
Report
Maker
@nartlg5 Hey Çınar! Actually, for the logistics integration on the internal ops tool, I didn't use FastAPI. I built the whole thing using the Next.js App Router.
To handle the schema differences, I essentially built my adapter layer using TypeScript—defining strict interfaces to ensure all the payloads perfectly match up before interacting with the external APIs.
As for rate limiting, I took a more front-end-driven approach: I implemented lazy loading for the orders across the various dashboards. This naturally staggers the data fetching as the user interacts with the UI, which keeps the API requests well within limits without needing a heavy queuing system on the backend.
Report
The sales automation tool caught my eye right away, the integration with logistics APIs sounds tricky and it looks like you handled it cleanly. Nice to see someone shipping real full-stack work instead of just pretty mockups.
Report
Maker
@burhanlbbm Hey Burhan! Thanks for your appreciation. Yeah, the API integration was tricky and followed many trials and errors. It wasn't even an proposed project in the organization. It was just I saw one of my co-worker putting the same data repetitively in billing and then the logistics dashboard. It was just a matter of fact that I checked, both have their APIs and thus spinned up a simple no backend form in a day to help him. Later the founders asked if we can have this or this, and this kind of flow and it eventually evolved into a full fledged project.
Hi Product Hunt! 👋
I’m excited to launch manasbhatia.me today. As someone balancing an EE degree with a role as a SDE, I wanted a clean, fast space to document my development journey.
My focus lately has been on cloud-native deployments (AWS EC2/S3/CloudFront), API integrations for billing and logistics, and speeding up development cycles with Next.js. And making full stack web and mobile applications using NextJs, FastAPI and React Native.
I’d love your feedback on the site’s performance, design, or any of the open-source projects listed. I'll be hanging out in the comments all day to answer questions!
Curious how you handle the logistics API integrations on the backend, are you wrapping FastAPI around them directly or building some kind of adapter layer to deal with rate limits and schema differences?
@nartlg5 Hey Çınar! Actually, for the logistics integration on the internal ops tool, I didn't use FastAPI. I built the whole thing using the Next.js App Router.
To handle the schema differences, I essentially built my adapter layer using TypeScript—defining strict interfaces to ensure all the payloads perfectly match up before interacting with the external APIs.
As for rate limiting, I took a more front-end-driven approach: I implemented lazy loading for the orders across the various dashboards. This naturally staggers the data fetching as the user interacts with the UI, which keeps the API requests well within limits without needing a heavy queuing system on the backend.
The sales automation tool caught my eye right away, the integration with logistics APIs sounds tricky and it looks like you handled it cleanly. Nice to see someone shipping real full-stack work instead of just pretty mockups.
@burhanlbbm Hey Burhan! Thanks for your appreciation. Yeah, the API integration was tricky and followed many trials and errors. It wasn't even an proposed project in the organization. It was just I saw one of my co-worker putting the same data repetitively in billing and then the logistics dashboard. It was just a matter of fact that I checked, both have their APIs and thus spinned up a simple no backend form in a day to help him. Later the founders asked if we can have this or this, and this kind of flow and it eventually evolved into a full fledged project.