I keep hearing, “You MUST start with a monolith.” Every new project? Always? When I hear that, two thoughts immediately come to mind: 1️⃣ “It depends.” You can’t just blindly say every project must start as a monolith. 2️⃣ My inner Dushnylo whispers: “Time to make a post about this.” So, here’s my take: I disagree. Not only do I disagree, but I believe the most critical and dangerous part of system design is analyzing and understanding business needs before making architectural decisions. Why? Simple. Imagine you’re building a streaming platform that processes massive amounts of data, handles notifications, and integrates with third-party services. Does this sound like something you’d build as a pure monolith? Of course not. But I do agree on one thing—you have to start somewhere. That starting point could be a simple core application —yes, it might look like a monolith at first. But you’re not designing the entire system as a monolith. ...
Platform to share knowledge, insights, and experiences with like-minded professionals. It’s not just about technical expertise—it’s about the journey from developer to leader, building successful teams, and transforming ideas into impactful solutions. Whether you’re looking for actionable advice, inspiration, or new perspectives, my goal is to provide valuable content for your professional growth.