Explore chapters and articles related to this topic
Cloud-Native Design
Published in Haishi Bai, Zen of Cloud, 2019
Another benefit of loose coupling is that a component can be replaced as needed without affecting other components, as long as the interfaces between components are faithfully implemented. For example, you've observed that an external service keeps failing to meet your reliability requirements and have found a replacement. If you've designed a stable provider interface, you can swap the services without impacting the rest of your system. Figure 2.15 shows a typical service provider pattern that uses a provider interface to encapsulate a service dependency. The example uses an IStateProvider interface to represent any storage services that can preserve states. A state provider implementation implements the interface and works with the proprietary storage API to work with a specific storage service.
Using a Virtual Engineering Environment for the Design and Development of a Compact Pilot Plant
Published in Fusion Science and Technology, 2021
The compact pilot plant consists of various critical components that are required to make the system operate. The architecture provided in Fig. 2 illustrates various components, some of which may be integrated into an existing system; others will need flexibility to add user-developed modules. As a result, coupling between elements needs to be defined. Coupling is defined as the degree of direct knowledge one module is required to know about another. In other words, the dependency between modules. Loose coupling references the minimal amount of dependency between components. On the other hand, tight coupling requires a strong dependency between and within modules. For the virtual engineering environment to be effective, loose coupling is required between models/elements. Tight coupling can be applied within a module to optimize performance.
Representing adaptation options in experimentable digital twins of production systems
Published in International Journal of Computer Integrated Manufacturing, 2019
Tim Delbrügger, Jürgen Rossmann
To extend this concept to the field of Digital Twins, the definition can be changed to include the complete cyber-physical system realisation with hard- and software, instead of just the software implementation. In this more general sense, the concept of loose coupling provides the possibility to change a specific subsystem within certain boundaries without the need for changes in other systems. Therefore, they provide essential flexibility for future Smart Factories and CPPS. Today, implementing such loose couplings is still a major problem for many domains. For example, decoupling a pick and place robot from specific types of workpieces is not trivial because today robot programs need to be developed or taught with a set of workpieces and their properties in mind.