At Samagra we have a user-service, which allows for easy and effective user-management. The task is to figure out the best way to expose this service so that we can use this same codebase in stencil without the need of writing wrappers around it.
Potential Solutions
Publish an SDK that has calls to the user-service exposed as functions
Add user-service as a separate microservice and use kong to redirect user related requests to this service directly? (not sure about the feasibility of this @ChakshuGautam please guide)
[My Suggestion] Publish the entire user-service as an npm-package and then do a npm install @SamagraX/user-service everytime it is required somewhere. Feasible??
Description
At Samagra we have a user-service, which allows for easy and effective user-management. The task is to figure out the best way to expose this service so that we can use this same codebase in stencil without the need of writing wrappers around it.
Potential Solutions
/metrics
endpoint, we can publish the required modules in theuser-service
in a similar manner and then register the module in the specific context and be able to use the exact same codebase without the need for wrapper services.