Creating a user information microservice
We could implement user authentication and accounts by simply adding a user model, and a few routes and views to the existing Notes application. While it would be easy to accomplish, is this what we would do in a real-world production application?
Consider the following considerations:
It's important to keep user identity data under tight security
The Notes application may be a small portion of a larger website; therefore, user authentication must be shared between multiple applications
The microservice approach—dividing the application into small chunks, each deployed as separate services—is a popular architecture choice that increases software development flexibility
It's claimed that the microservice approach is easier to manage than when developing a monolithic large application. By dividing the total system into small services, each service can be developed by a small team, whose engineers can fully grow their service, with each able to proceed on...
