Our current Bharat Seva+ project has both healthcare and user functionalities tightly coupled in the same service. Thus to improve modularity, maintainability, and scalability, we need to separate the healthcare functionality.
Proposal
All healthcare related code and logic (authentication, user profile management, etc.) will be moved from the current service into a new microservice dedicated to handling healthcare related functionality.
Key Benefits
Scalability: healthcare functionalities can be scaled independently.
Maintainability: Code for each functionality is isolated, making it easier to modify or enhance without impacting the other.
Clear Separation of Concerns: The healthcare will be more focused, leading to a more organized codebase.
Tasks
Create healthcare related logic from the current service.
Set up a new server that manages healthcare request only, microservice for healthcare functionality.
Build in Golang language, easy to understand, scale, add new features with optimized performance.
Write test cases for the new service.
Additional Notes
We do not need to make separate APIs endpoints for healthcare just use the current API endpoints (you can take help from postman for endpoints).
In Golang, use frameworks like Echo (Preferable) or Gin.
Make proper documentation and add meaningful comments to explain each components.
Before taking this issue, please explain how you will approach this task, what steps are you going to take and do you've any previous experience in building webserver with Golang ?
Description
Our current Bharat Seva+ project has both healthcare and user functionalities tightly coupled in the same service. Thus to improve modularity, maintainability, and scalability, we need to separate the healthcare functionality.
Proposal
Key Benefits
Tasks
Additional Notes
Before taking this issue, please explain how you will approach this task, what steps are you going to take and do you've any previous experience in building webserver with Golang ?