Pluggable-approach-for-Mappers-and-Drivers.md

@@ -10,10 +10,12 @@ The solution is built upon two primary pillars: the extensive use of the Spring
 
 Key points:
 
-- **Creating a Standalone Driver Jar**: The solution allows the Driver jar to function as a standalone artifact with all the necessary components for proper operation. The Driver is responsible for assembling data sources, maintaining them, and providing their unique dependencies.
-- **Dynamic Dependency Wiring**: This solution enables dynamic dependency wiring at runtime, allowing for the swapping of dependencies as needed. The OSDU service relies on the Driver's self-sufficiency, which involves autonomous component assembly within the Driver. This approach fosters a loose coupling that allows for dependency swaps without requiring changes in the service.
-- **Plugin usage is not mandatory**. Provider implementations could use community Drivers and their own Drivers as direct dependencies of their service implementation. The compile step configured for community Drivers is not mandatory for provider Drivers. Furthermore, the community Drivers will have 2 artifacts, the original jar which could be used as a regular dependency, and the Uber jar or plugin jar.
-  
+- **Creating a Standalone Driver Jar**: The solution allows the Driver jar to function as a standalone artifact with all the necessary components for proper operation. The Driver is responsible for assembling data sources, maintaining them, and providing their unique dependencies. <br/>
+![Untitled_Diagram.drawio_13_](uploads/50f0bf9cb26b486f5fba38ac2334b402/Untitled_Diagram.drawio_13_.png)
+- **Dynamic Dependency Wiring**: This solution enables dynamic dependency wiring at runtime, allowing for the swapping of dependencies as needed. The OSDU service relies on the Driver's self-sufficiency, which involves autonomous component assembly within the Driver. This approach fosters a loose coupling that allows for dependency swaps without requiring changes in the service. <br/>
+![Untitled_Diagram.drawio_14__1_](uploads/c81ada18daa4a7ef5474a26cf5d5c467/Untitled_Diagram.drawio_14__1_.png)
+- **Plugin usage is not mandatory**. Provider implementations could use community Drivers and their own Drivers as direct dependencies of their service implementation. The compile step configured for community Drivers is not mandatory for provider Drivers. Furthermore, the community Drivers will have 2 artifacts, the original jar which could be used as a regular dependency, and the Uber jar or plugin jar. <br/>
+![Untitled_Diagram.drawio_15_](uploads/c3f9a1046e226dffb412388ee7186a4c/Untitled_Diagram.drawio_15_.png)
 ### 3. Use Cases
 
 #### Common Binaries and Custom Drivers: