<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vedant Panchal on Medium]]></title>
        <description><![CDATA[Stories by Vedant Panchal on Medium]]></description>
        <link>https://medium.com/@vedantwork1402?source=rss-2865d6f29ecc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oHLpp8g6pWn7k21q</url>
            <title>Stories by Vedant Panchal on Medium</title>
            <link>https://medium.com/@vedantwork1402?source=rss-2865d6f29ecc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:14:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vedantwork1402/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Two Multi-Tenant Enterprise Platforms in Eight Weeks at IIIT Bangalore]]></title>
            <link>https://medium.com/@vedantwork1402/building-two-multi-tenant-enterprise-platforms-in-eight-weeks-at-iiit-bangalore-c4f6eec0ecce?source=rss-2865d6f29ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4f6eec0ecce</guid>
            <category><![CDATA[summer-internships]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[multitenancy]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[keycloak]]></category>
            <dc:creator><![CDATA[Vedant Panchal]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 12:26:41 GMT</pubDate>
            <atom:updated>2026-11-17T12:26:41.242Z</atom:updated>
            <content:encoded><![CDATA[<p>What a College ERP, an HRMS, and a lot of Keycloak debugging taught me about real software engineering.</p><p>When I joined IIIT Bangalore for my summer internship (1 June to 31 July 2026), I expected a coding project. What I got was a design problem. The brief from my guide, Prof. Chandrashekar Ramanathan, was to build software that several organisations could share without ever seeing each other’s data. I ended up building two systems: a <strong>College Administration ERP</strong> and a <strong>Universal Human Resource Management System (UHRMS)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvbvdeKjHMNeT9P0jiNUaw.png" /></figure><h3>Why multi-tenancy changes everything</h3><p>Both platforms are multi-tenant. One deployed instance serves many colleges or organisations, and a user from one must never see another’s data, not even in an error message.</p><p>Every college-scoped row carries a tenant_id. A filter early in the Spring Security chain reads the tenant from the validated JWT, stores it in a TenantContext, and every repository query is scoped to it. Cross-tenant reads return 404, not someone else’s data.</p><p>The lesson I took from this is that multi-tenancy is a design constraint, not a feature flag. Every query, ID lookup, and error path has to respect it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsMjyrdN6iKQ0z-Iswl7bA.png" /><figcaption>system architecture diagram from the College ERP</figcaption></figure><h3>The stack</h3><ul><li><strong>Backend:</strong> Java 21, Spring Boot 3.3 (ERP) and 3.4.5 (UHRMS), Spring Security 6, Spring Data JPA</li><li><strong>Identity:</strong> Keycloak (OIDC/OAuth2, JWT resource server)</li><li><strong>Database:</strong> MySQL 8 with Flyway migrations</li><li><strong>Frontend:</strong> React 18, Vite, Axios, keycloak-js</li><li><strong>DevOps:</strong> Docker Compose, GitHub Actions, GHCR</li></ul><h3>Project 1: College ERP</h3><p>The ERP covers four areas: academics, examinations, campus placements, and identity and audit. It supports eight roles, from PLATFORM_SUPER_ADMIN to STUDENT and RECRUITER.</p><p><strong>The seating algorithm.</strong> A naive round-robin put students taking the same paper next to each other. I switched to an interleaving strategy that alternates students across course offerings and halls, and excludes barred students. I kept it as a standalone service class so it could be unit-tested in isolation.</p><p><strong>The eligibility engine.</strong> When a student applies to a placement drive, the system checks minimum CGPA, maximum active backlogs, allowed branches, and graduation year. The result is available through the API before the student applies.</p><h3>Project 2: UHRMS</h3><p>The UHRMS is a domain-independent HR backend. It is a modular monolith split into <em>Foundation</em> modules (identity, org structure, workflow, documents, notifications) and <em>HR Process</em> modules (requisition, recruitment, onboarding, leave, attendance, exit). Its schema grew to 13 Flyway migrations.</p><p>The part I enjoyed most was the workflow engine. It is a generic multi-stage approval engine (DRAFT → SUBMITTED → IN_PROGRESS → APPROVED/REJECTED), so leave, requisitions, and exits all reuse the same approval logic.</p><p>The recruitment-to-onboarding link is event-driven. When a candidate is marked JOINED, the system publishes a CandidateJoinedEvent. The onboarding module listens, creates a case, seeds a checklist, and sends a welcome notification. The two services never call each other directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4P0sYN6HeUjijEaiquNGkQ.png" /><figcaption>the recruitment-to-onboarding sequence diagram</figcaption></figure><h3>What broke, and what I learned</h3><p><strong>The missing </strong><strong>tenant_id claim.</strong> Logins worked, but every tenant API returned 403. The cause was Keycloak’s user profile config, which was dropping my custom attribute. I enabled unmanaged attributes, added a protocol mapper, and wrote a script (ensure_demo_users.py) so the setup was reproducible.</p><p><strong>Orphaned users after realm re-import.</strong> Keycloak issued new sub IDs and my local accounts stopped matching. I made the filter fall back to email matching and re-link the account.</p><p><strong>Three IDs that are not one.</strong> The Keycloak sub, the local user ID, and the student profile ID are all different. Mixing them up caused the subtlest bugs of the summer.</p><p><strong>Dev mode is not production.</strong> I moved Keycloak off start-dev onto a MySQL-backed production overlay, disabled Swagger in the prod profile, and bound Keycloak to loopback.</p><h3>Testing and shipping</h3><p>Unit tests cover the seating, grading, and eligibility logic, and integration tests cover tenant isolation and full workflows. On top of that I wrote PowerShell QA scripts that run the exam and placement lifecycles end to end, check the role matrix, and verify that a second tenant cannot read the first tenant’s data. GitHub Actions runs the tests on every PR and publishes images to GHCR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfj0F2v6L8-W-QV_TFzFXg.png" /><figcaption>GitHub Actions run</figcaption></figure><h3>What I’m taking away</h3><ol><li>Identity is part of the product. Claims and roles in Keycloak matter as much as the business tables.</li><li>Automation buys confidence. QA scripts caught issues unit tests never would, such as issuer mismatches and CORS.</li><li>“Done” means deployable, recoverable, and documented, not just working on my laptop.</li><li>Real integrations beat mocks for security-critical paths.</li></ol><p>I’m grateful to Prof. Ramanathan for the freedom to make real architectural decisions and the standard to defend them. Both repositories are public:</p><ul><li>College ERP: <a href="https://github.com/VedantPanchal23/ctri-dg_college-ERP">https://github.com/VedantPanchal23/ctri-dg_college-ERP</a></li><li>UHRMS: <a href="https://github.com/VedantPanchal23/ctri-dg_urms">https://github.com/VedantPanchal23/ctri-dg_urms</a></li></ul><p><em>Vedant Panchal, B.Tech AI &amp; ML, CSPIT (CHARUSAT)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4f6eec0ecce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code to containers: My Internship Journey working on Docker and the MERN Stack]]></title>
            <link>https://medium.com/@vedantwork1402/code-to-containers-my-internship-journey-working-on-docker-and-the-mern-stack-d3e2b46ec5d7?source=rss-2865d6f29ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3e2b46ec5d7</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[summer-internships]]></category>
            <dc:creator><![CDATA[Vedant Panchal]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 07:58:20 GMT</pubDate>
            <atom:updated>2025-08-29T07:58:20.861Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This summer, I interned at HUDE Labs IT Solutions Pvt. Ltd. as a Software Development Intern and it was one of the best experiences of my career in academics up till now.</blockquote><p>The interesting part of this internship was that it was not only about me writing code — I was also in charge of Dockerizing and running each one of the projects that I handled. In weeks, from testing basic APIs through managing multi-container MERN stack applications based on Docker Compose, I progressed.</p><p>This is how that journey went.</p><p><strong>Getting Started at HUDE Labs</strong></p><p>HUDE Labs, from Bhopal, is a company that is rapidly scaling up smart city solutions and digital services. Startup-like culture that it was, it did not tie me up for doing “intern tasks.” Rather, it provided me ownership of actual tasks and left me to figure out actual deployment problems.</p><p>That’s when Docker entered the picture.</p><p><strong>The Projects That I Built &amp; Dockerized</strong></p><ol><li><strong>TestApp — My First Dockerized App</strong><br>This was also my intro to containerization — a Node.js + MongoDB app in which users registered and fetched their data.<br><strong>My Docker effort:</strong><br>1. Created a Dockerfile for the backend.<br>2. Configured MongoDB with YAML.<br>3. Ensured seamless communication between containers.<br><br>It was simple, and it taught me Docker resolved the classic “works on my machine” problem.</li><li><strong>DevNotes — A Complete-Stack Note-Taking System</strong><br>That was followed by DevNotes, a developer note taking system that featured authentication, markdown support, and CRUD operations.<br><strong>My Docker Work:<br></strong>1.<strong> </strong>Containerized frontend (React), backend (Express), and database (MongoDB).<br>2. Utilized Docker Compose for service orchestration.<br>3. Set up NGINX as a reverse proxy for clean routing.<br>4. Mounted volumes for retaining notes over container restarts.<br><br>This was my first real-world experience of deploying a microservices-like app.</li><li><strong>MERN Ecommerce — A Complete E-Commerce Solution<br></strong>Finally, I built a MERN stack e-commerce system that included product listings, shopping cart, authentication, and order submission.<br><strong>My Docker Project:<br></strong>1. Created optimized Dockerfiles for frontend and backend.<br>2. Created a docker-compose.yaml file to launch client, server, and database simultaneously.<br>3. Env management for secrets and configs.<br>4. Managed steady volumes &amp; networking for redundancy.<br><strong>The ultimate moment? Running:<br></strong><em>docker-compose up — build<br></em><br>…and watching the entire platform come alive within seconds.</li></ol><p><strong>What I Learned</strong></p><p>Owning the Docker work for every project gave me lessons I’ll carry forward:</p><ul><li><strong>Containerization = consistency</strong>: Apps run the same on dev, test, and production.</li><li><strong>Orchestration matters</strong>: Docker Compose taught me to manage multi-service apps.</li><li><strong>Think beyond code</strong>: Real-world development is also about deployment, scaling, and reliability.</li><li><strong>Debugging makes you stronger</strong>: Fixing container networking and lifecycle issues made me a better problem-solver.</li></ul><p><strong>Wrapping Up</strong></p><p>This internship wasn’t just about building apps — it was about <strong>learning how to ship them reliably</strong>. Docker gave me the confidence to handle deployment challenges, while the MERN stack projects sharpened my full-stack skills.</p><p>Now, when I approach software engineering, I don’t just think about features. I think about <strong>how to package, deploy, and scale them in production</strong>.</p><p>And that mindset, I believe, is what will set me apart as I continue my journey in software development and DevOps.</p><blockquote><em>Thanks for reading! If you found this useful, feel free to share it with someone starting out with Docker or the MERN stack.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3e2b46ec5d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>