EngineConn architecture design
EngineConn architecture diagram
Introduction to the second-level module:
linkis-engineconn-common engine connector common module
Define the most basic entity classes and interfaces in the engine connector. EngineConn is used to create a connection session for the underlying computing storage engine, which contains the session information between the engine and the specific cluster, and is the client that communicates with the specific engine.
Core Service | Core function |
---|---|
EngineCreationContext | Contains the context information of EngineConn during startup |
EngineConn | Contains the specific information of EngineConn, such as type, specific connection information with layer computing storage engine, etc. |
EngineExecution | Provide Executor creation logic |
EngineConnHook | Define the operations before and after each phase of engine startup |
Defines the interfaces involved in the core logic of EngineConn.
linkis-engineconn-launch engine connector startup module
Core class | core function |
---|---|
EngineConnServer | EngineConn microservice startup class |
linkis-callback-service callback logic
Core Class | Core Function |
---|---|
EngineConnCallback | Define EngineConn’s callback logic |
Executor that can be accessed. You can interact with it through RPC requests to get its status, load, concurrency and other basic indicators Metrics data.