From the course: Web Components and Modularization: Practical Approaches
Unlock the full course today
Join today to access over 24,700 courses taught by industry experts.
Isolation principle
From the course: Web Components and Modularization: Practical Approaches
Isolation principle
- [Instructor] The isolation principle is not absolutely rigid, but should be adhered to whenever possible. It says that a component should not care about or know about what's happening around it with other components. It shouldn't know anything about the state or statelessness of other components. It shouldn't care if they are defined as functions or classes. It shouldn't be influenced by anything happening outside of itself. Each component should be an island unto itself, receiving input and sending output as required. This principle actually dates all the way back to the layered system principle of REST architecture. individual components cannot see beyond the immediate layer with which they are interacting and has no knowledge or care for what lies beyond. The isolation principle has several important benefits. Isolated components don't rely on the output of other components to function. Isolated components can be used…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.