On Nov 2, 2017, at 2:11 AM, Shenoy, Gourav Ganesh <[email protected]<mailto:[email protected]>> wrote:
* Another point which comes to my mind is about moving away from this big “API Server” block and segregating into smaller service level first class SDKs. For e.g.: We now have a first class “Profile Service” which allows isolated interactions pertaining to Users, Tenants and Groups. We might want to keep these SDKs / services as independent as possible, which also means no reliance on messaging. Will the architecture support these SDKs? Gourav and others, This is somewhat off topic, but something I never really understood, why did we decide to break apart the API server? I think having a single API for Airavata has some advantages. Creating and using a client is simplified since there is only one API. Also securing the API is something that can be done once instead of over and over with each service’s API. I could understand multiplexing the API server’s handlers to cut down on the size of handler code. But that doesn’t require breaking up the API server to multiple service level APIs. Thanks, Marcus
