Member-only story
🐏 Angular Modules Dark Side: The Black Sheep Of Enterprise Apps. Ditch Them
Many organisations have to decide if they stick with NgModules in their enterprise applications. While it’s tempting, they add complexity and duplicate hierarchies. Should you reorganize or ditch them? Let’s find out!
Four days ago I’ve published an article urging to switch to standalone components due to the benefits they give for Angular scalable applications. But I skipped one important part regarding bigger organisations. So let’s clarify that.
By the way, my name is Tom Smykowski. I’m an expert in building scalable enterprise applications, and I’ve worked on large-scale Angular projects with cross-functional teams of dozens of developers, serving millions of users globally. In this series, I’ll share the key strategies to help you build Angular apps that scale efficiently and stand the test of time.
Currently there’s a lot of Angular apps, large Angular enterprise apps, that use modules. For these organisations decision if and how switch to standalone components may be more complicated than for new apps.
