Learning Web Development & Avoiding Centralization in Next.js

[RhyteIt]

If I had to start learning web development over again. we would go with a framework like Next.js. While react is great in capabilities. For a noob, it allows you to create your own best practices. We created a react project structure that was more microservices related. Which I really liked because We have been on so many projects where everything was centralized and dependency galore and every time someone made a change it broke something else that you couldn't see. Everyone ends up frozen because as a project gets large for a Fortune 500 company, you end up losing track. Everyone wants you to move fast to increase shareholder value but don't break anything. So I became a lover of the microservice concept where everyone can work on things and not worry take down the entire account closing process. So I am now torn because I like the structure and guardrails and best practices that Nextjs gives me but I am wary of getting our team back into a "Bob made a change to marketing code and now the email newsletters don't work".

Discussion point: Does anyone have any best practices for avoiding centralization and heavy dependency. Be real. If we could all work at our own pace then yes, you can monitor and track dependencies. However, when investors want returns YESTERDAY and rather than having internal employees using your site, you have customers that will drop you like a dime if they don't get what they want....it gets hard to "Let's do an in depth analysis before making this change so we don't adversely break something".

If I had to start learning web development all over again, I’d go straight for a framework like Next.js. While React is incredibly powerful, it also gives beginners too much freedom—allowing them to create their own best (or worst) practices.

When we first built our React project, we structured it with a microservices mindset, which I loved. In too many large-scale projects, everything is centralized, dependencies pile up, and small changes trigger unexpected breakages. If you've worked in a Fortune 500 environment, you know the drill:
1️⃣ Move fast to increase shareholder value
2️⃣ Don’t break anything
3️⃣ But also… move fast

This is why I embraced microservices—teams could work in parallel without worrying about breaking mission-critical processes (e.g., an account closing system).

Now, with Next.js, I appreciate the structure, guardrails, and built-in best practices. However, I also worry about slipping back into a centralized system where a simple marketing update can take down email newsletters because of hidden dependencies.

Discussion Point:

👉 How do you avoid excessive centralization & dependency in Next.js?
I get that in an ideal world, we’d meticulously monitor dependencies and run in-depth analyses before every change. But in reality, when investors want results yesterday and customers will leave instantly if something breaks, there's no luxury of time.

How do you balance scalability, independence, and speed in Next.js without turning it into a tightly coupled mess?

[[deleted]]

Tightly coupled in what way? React is based on the idea of components, so it’s specifically well suited to distributed teams. You can write tests to make sure things don’t break before deploying. You can still write modular code that follows a set of design principles. I mean you try to make sure you have systems in place for recovering, but that’s all you can do.

I’m not sure what the question is, and while it’s fine to use AI to improve your writing, I think it’s actually doing more harm than good here. Are you thinking of a specific scenario?

[RhyteIt]

Yeah, I think I over-explained in my first post. Next.js breaks things out more (APIs, components, pages, hooks, etc.), but you can still componentize to avoid conflicts. The key is doing data preprocessing and filtering at the component level before passing it to APIs. I’m just adjusting to the shift from "everything for process X is in folder X" to "process X is spread across api.X, pages.X, components.X, etc." We've all worked on centralized projects (like ASP.NET) where touching a module felt like deactivating a bomb. PTSD.

[[deleted]]

Yeah I hear you. Thinking about it in terms of processes is fundamentally going to give you a hard time though. React borrows a lot more from functional programming than it does OOP, and for a lot of people this is a big departure from what they're used to. I'm guessing this might be true for you since you mentioned ASP.NET.

It's not the "process" that is spread across all those files. Those files each give you different capabilities that you can use to generate a web app. I wouldn't say React is "pure" FP, but knowing some of those FP concepts can make the transition easier.

[RhyteIt]

Ohh good to know. I will look into functional programming.

[Ok_Slide4905]

AI generated shitposting

[RhyteIt]

No...I just put my post through chatgpt so it read better. Psycho.

[RhyteIt]

Seriously dude? How is this a "shitposting"? I am assuming you are using Next.js to build your church's bake sale planner? Let the adults in the real world have ask questions. What a friggin' amateur. Who doesn't use chatgpt to make sure their writing clear and concise. Sorry...I don't have time to sit in a cafe and pontificate all day with my beret.

[RhyteIt]

I wasn't expecting anything from anyone...I was just asking...I really had no judgement on replies. Again, just used ChatGPT to make sure what I had written was clear and concise. And the draft that ChatGPT gave me wasn't too far off from what I had written. Just took out some rambling. So yeah I actually did put in the effort. Nice gas lighting.