-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project 1 Feedback from Team Zilean #75
Comments
|
I agree with Tanu but I think the professor suggested that we should develop user and session microservice differently because that is a scalable design because if in the future you have millions of users then it will distribute load properly
|
We kept this in mind and tested RabbitMQ for asynchronous communication between API Gateway and Plotting Service since those are the most heavy lifters, but due to lack of our knowledge in it we were not able to pursue it. Either way its a good point from a point of scalability, which we'll definitely try to achieve the next time. I agree with the scalable thing, but multiple network calls can simultaneously make the system very slow and both the data are very inter-related. Professor mentioned we can have two micro services as to show internal communication among them but we are fulfilling the same purpose among gateway and other services. |
Thanks for your feedback Rushikesh and Aishwarya! |
System design is good and efficient. Also, dockerizing microservice is a commendable task and it works properly. Having user and session logic in one microservice is good but could have made 2 microservices out of it. Actually, both ways are correct but we went with the later one. Below are some observations from our side.
Pros:
Cons:
Thanks
Team Zilean
The text was updated successfully, but these errors were encountered: