Browse Source

fix: add consequence of adapter implementation

Signed-off-by: Moritz Johner <beller.moritz@googlemail.com>
Moritz Johner 8 months ago
parent
commit
d0756bb7c1
1 changed files with 2 additions and 0 deletions
  1. 2 0
      design/014/ADAPTER.md

+ 2 - 0
design/014/ADAPTER.md

@@ -115,6 +115,8 @@ The architecture employs a global connection pool (`grpc.ConnectionPool`) to ena
 - **Flexibility:** Providers can be deployed in-process (legacy), out-of-process (v2), or mixed
 - **Flexibility:** Providers can be deployed in-process (legacy), out-of-process (v2), or mixed
 - **Testability:** v1 provider implementations can be tested directly without gRPC infrastructure
 - **Testability:** v1 provider implementations can be tested directly without gRPC infrastructure
 - **Gradual Migration:** Existing providers migrate individually without disrupting others
 - **Gradual Migration:** Existing providers migrate individually without disrupting others
+- **New features**: This will open the door to provider implementations. Alternative deployments designs are possible, though they are not the goal of this design.
+
 
 
 ### Negative
 ### Negative