Moh Ramjan’s Post

Zurl is live. I built a URL Shortener with Java Spring Boot and deployed it. Here's what the final product looks like: You paste a long URL -> Zurl gives you a short one -> anyone who clicks it gets redirected instantly -> every click gets tracked. That's the surface. Under the hood: The shortening service and redirection service are completely separate. One handles creating short URLs, the other handles redirecting. They don't talk to each other -> they just share a PostgreSQL database. This means if redirection traffic spikes (reads are always 100x more than writes), I can scale just that service without touching the shortening logic. Short URLs are generated using Base62 encoding on a counter value. 6 characters -> 56 billion possible combinations. Zero collisions by design. The redirect returns 302 instead of 301. This one decision is what makes the analytics work. 301 gets cached by the browser and your server never sees repeat visits. 302 hits the server every time -> every click gets recorded in the Client Event table. JWT authentication makes sure only logged in users can create and manage their own links. Every user owns their URLs. Three months ago I didn't know what a 302 redirect was. Now I've built and deployed a system that depends on it. The live link is available in the comments. #Java #SpringBoot #BackendDevelopment #BuildInPublic #OpenToWork

🗂️ 𝗝𝗔𝗥 𝘃𝘀 𝗪𝗔𝗥 𝘃𝘀 𝗘𝗔𝗥 — 𝗝𝗮𝘃𝗮 𝗣𝗮𝗰𝗸𝗮𝗴𝗶𝗻𝗴 𝗗𝗲𝗺𝘆𝘀𝘁𝗶𝗳𝗶𝗲𝗱! If you've ever stared at a Java project wondering "what even is this file?" — this one's for you. 👇 As Java developers, we deal with these three archive types constantly, but many beginners (and even some seniors!) mix them up. Let's break it down simply: 📦 𝐉𝐀𝐑 — 𝐉𝐚𝐯𝐚 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 The most basic building block. Think of it as a zip file for your Java classes and resources. ✅ Used for: Libraries, utilities, standalone apps 🔧 Server: Any JVM 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: commons-lang.jar, jackson-databind.jar 🌐 𝐖𝐀𝐑 — 𝐖𝐞𝐛 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 Everything you need to deploy a web application. It's a JAR — but supercharged with web goodies: Servlets, JSPs, HTML, CSS, JS & WEB-INF config. ✅ Used for: Web applications 🔧 Server: Tomcat, Jetty, Undertow 🏢 𝐄𝐀𝐑 — 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 The big boss of Java packaging. An EAR can contain multiple WARs + JARs (EJB modules) under one roof — perfect for large enterprise systems. ✅ Used for: Full-scale enterprise applications 🔧 Server: JBoss, WildFly, WebLogic 🔑 𝐆𝐨𝐥𝐝𝐞𝐧 𝐑𝐮𝐥𝐞 𝐭𝐨 𝐑𝐞𝐦𝐞𝐦𝐛𝐞𝐫: JAR ⊂ WAR ⊂ EAR Each level wraps the previous one. Start simple, scale when needed. 💬 Drop a comment — are you still deploying WARs or have you moved to containerized JARs with Spring Boot? Let's talk! #Java #JavaDeveloper #SpringBoot #WebDevelopment #SoftwareEngineering #BackendDevelopment #Programming #100DaysOfCode #TechTips #JavaEE #JVM #LearnToCode #DevCommunity #CodeNewbie #CleanCode

🗂️ 𝗝𝗔𝗥 𝘃𝘀 𝗪𝗔𝗥 𝘃𝘀 𝗘𝗔𝗥 — 𝗝𝗮𝘃𝗮 𝗣𝗮𝗰𝗸𝗮𝗴𝗶𝗻𝗴 𝗗𝗲𝗺𝘆𝘀𝘁𝗶𝗳𝗶𝗲𝗱! If you've ever stared at a Java project wondering "what even is this file?" — this one's for you. 👇 As Java developers, we deal with these three archive types constantly, but many beginners (and even some seniors!) mix them up. Let's break it down simply: 📦 𝐉𝐀𝐑 — 𝐉𝐚𝐯𝐚 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 The most basic building block. Think of it as a zip file for your Java classes and resources. ✅ Used for: Libraries, utilities, standalone apps 🔧 Server: Any JVM 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: commons-lang.jar, jackson-databind.jar 🌐 𝐖𝐀𝐑 — 𝐖𝐞𝐛 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 Everything you need to deploy a web application. It's a JAR — but supercharged with web goodies: Servlets, JSPs, HTML, CSS, JS & WEB-INF config. ✅ Used for: Web applications 🔧 Server: Tomcat, Jetty, Undertow 🏢 𝐄𝐀𝐑 — 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐑𝐜𝐡𝐢𝐯𝐞 The big boss of Java packaging. An EAR can contain multiple WARs + JARs (EJB modules) under one roof — perfect for large enterprise systems. ✅ Used for: Full-scale enterprise applications 🔧 Server: JBoss, WildFly, WebLogic 🔑 𝐆𝐨𝐥𝐝𝐞𝐧 𝐑𝐮𝐥𝐞 𝐭𝐨 𝐑𝐞𝐦𝐞𝐦𝐛𝐞𝐫: JAR ⊂ WAR ⊂ EAR Each level wraps the previous one. Start simple, scale when needed. 💬 Drop a comment — are you still deploying WARs or have you moved to containerized JARs with Spring Boot? Let's talk! #Java #JavaDeveloper #SpringBoot #WebDevelopment #SoftwareEngineering #BackendDevelopment #Programming #TechTips #JavaEE #JVM #LearnToCode #DevCommunity #CodeNewbie #CleanCode

After 9 years building Java backends, here are my REST API design rules that I wish I knew on day 1: 1. Version your APIs from the start   /api/v1/users not /api/users   Future you will thank present you 2. Use proper HTTP status codes   201 for created, 204 for no content   Stop returning 200 for everything 3. Paginate ALL list endpoints   ?page=0&size=20 is not optional   Learned this after a 50k record response crashed a client 4. Never expose your database IDs   Use UUIDs in your API responses   Internal IDs are an implementation detail 5. Document with OpenAPI/Swagger FIRST   Design the contract before writing code   Your frontend team will love you 6. Return meaningful error messages   {"error": "User not found", "code": "USR_404"}   Not just a 500 with a stack trace The best APIs are boring. Consistent, predictable, well-documented. What REST API rule would you add? #Java #SpringBoot #REST #API #BackendDevelopment #SoftwareEngineering

 I’ve spent most of my career feeling like a junior... until I started seeing the Fractals. 🌀🔬 Yusuf Kaya's post on the 5 layers is a great map for building real things. It’s the standard for a reason. 🗺️ But because of my neurodivergent profile, my brain doesn't stop at "Hosting." I’m constantly looking for the hidden cues and the deeper connections. I can't help it—I think in Fractals. When I look at those 5 layers, I start seeing the dimensions below them that we usually ignore: Below Hosting: I see a Consensus Layer. How do nodes talk when the "King Fish" (the central server) dies? 🏛️📡 Below Logic: I see the Immutable Log. Why are we chasing "heisenbugs" in mutable variables when we could just record the truth and never delete it? 📜⚖️ Below Security: I see Physics. Software is a guess; a hardware kill-switch (The Silicon Warden) is a fact. 🛡️⚙️ Below the App: I see Metabolism. Every CPU cycle is energy. If our code doesn't respect the "Hormonal Signaling" of the power grid, we’re just building parasites. ⚡💹 I don’t consider myself a "10x Developer" or some "Senior Guru." I’m just a guy in El Salvador building from zero who realized that relief is not the same as a cure. 🇸🇻🧪 Most of us are trained to fix symptoms in the top layers. But if you have the "curse" of seeing the deeper invariants, you realize we’re all playing 12D Chess—whether we’re looking at the board or not. 🧩 Don't just master the layers. Explore the Sovereignty underneath them. That’s where the real "Definitive Cure" for our infrastructure lives. #BuildingInPublic #Neurodiversity #FractalThinking #KuboLabs #ZeroToOne #SoftwareEngineering #12DChess

🚀 Mastering the Servlet Life Cycle in Java ✔️Ever wondered what happens behind the scenes when you hit a URL? If you're working with Java web applications, understanding the Servlet Life Cycle is non-negotiable. ✔️Managed by the Servlet Container (like Apache Tomcat), a servlet doesn't just "run"—it lives through a specific journey. 🎭 The 3 Main Stages 1️⃣. Initialization: init() The container calls this method exactly once. It’s the "birth" of the servlet. This is where you initialize resources like database connections or global variables. Fun fact: If init() fails, the servlet is dead on arrival! 2️⃣. Handling Requests: service() This is the "working life" of the servlet. For every incoming request, the container calls this method. It determines the HTTP type (GET, POST, etc.) and dispatches it to the corresponding doGet() or doPost(). Key point: It runs in a multi-threaded environment, so keep it thread-safe! 3️⃣. Destruction: destroy() The "retirement" phase. Before the container shuts down or removes the servlet, it calls destroy(). Use this to clean up—close those DB connections and release memory. 💻 A Quick Visual in Code public class MyServlet extends HttpServlet { public void init() { // One-time setup System.out.println("Servlet is born!"); } protected void doGet(HttpServletRequest req, HttpServletResponse res) { // Handling the work System.out.println("Servlet is serving a request..."); } public void destroy() { // Final cleanup System.out.println("Servlet is shutting down."); } } 💡 Why does this matter? Understanding these stages helps you write memory-efficient and performant code. Don't open a new DB connection in service() (expensive!); do it once in init()! ❓What's your favorite tip for optimizing Java Servlets? Let's discuss in the comments! 👇 #Java #WebDevelopment #Backend #Servlet #CodingTips #SoftwareEngineering #TechCommunity

☕ JAR vs WAR vs EAR - Know Your Java Packaging In Java enterprise development, choosing the right packaging can save you time, resources, and deployment headaches. 🔹 JAR for simple Java apps & reusable libraries 🔹 WAR for web applications 🔹 EAR for complete enterprise solutions Right tool, right place. That’s how we build scalable & maintainable systems. What’s your go-to packaging in projects? #Java #SoftwareDevelopment #BackendDevelopment #CleanArchitecture #Engineering

☕ JAR vs WAR vs EAR - Know Your Java Packaging In Java enterprise development, choosing the right packaging can save you time, resources, and deployment headaches. 🔹 JAR for simple Java apps & reusable libraries 🔹 WAR for web applications 🔹 EAR for complete enterprise solutions Right tool, right place. That’s how we build scalable & maintainable systems. What’s your go-to packaging in projects? #Java #SoftwareDevelopment #BackendDevelopment #CleanArchitecture #Engineering

🚀 Day6 of Advanced Java Learning Journey……. Today’s session helped me understand how Java web applications actually work internally 🌐💻 🔹 What is a Servlet? A Servlet is a Java program that runs on the server and handles client requests, generating dynamic responses. 👉 It plays a key role in building web applications 🔹 Servlet Life Cycle :- ✔️ init() – Runs once for initialization ✔️ service() – Handles every client request ✔️ destroy() – Cleans up resources 💡 Managed completely by the Servlet Container (like Tomcat) 🔹 GenericServlet vs HttpServlet 👉 GenericServlet :- Protocol independent Basic usage 👉 HttpServlet :- Designed for HTTP requests Uses doGet() & doPost() Most widely used 🔹 Types of Logic in Applications 🔸 Presentation Logic – User interface (HTML, CSS, JS) 🔸 Business Logic – Core processing (Servlets, JSP) 🔸 Data Access Logic – Database interaction (JDBC) 💡 Dividing logic makes applications clean and scalable 🔹 Standalone vs Web Applications 👉 Standalone Apps Run on a single system Used by one user 👉 Web Apps Run on servers Accessible via browser Supports multiple users 🔹 Types of Web Applications ✔ Static Web Apps – Same content for all users ✔ Dynamic Web Apps – Content changes based on user input 🎯 NOTE : Understanding servlets and application layers gave me a clear idea of how frontend, backend, and database work together #AdvancedJava #Servlets #JavaLearning #Day6 #BackendDevelopment #WebDevelopment #CodingJourney 🚀 Guided by, Anand Kumar Buddarapu sir, Saketh Kallepu sir, Uppugundla Sairam sir.