Session

The Hidden Powers of enforcing NX Module Boundaries (Case Study)

The more people work simultaneously on a particular codebase, the bigger the need for communication: the challenges, the ideas, and finally the changes. Having multiple teams co-creating a complex frontend system can get very challenging not to create a tangled web of unnecessary dependencies, as we move forward.

Let me share my findings from analyzing an enterprise-scale platform which suffered from such issues. Let's see how much we can improve systems if we pay enough attention to 2 well knows NX features: the "nx graph" and the "nx module boundaries".

Tomasz Ducin

Independent Consultant & Architect at Ducin.dev

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top