Identity and Authentication - Third Party Auth Systems

Third Party Auth Systems

Most of the risk lies in our back-end, where the user is making a request, our server is attempting to find our ground truth, and determining whether or not that user is who they say they are.

---

Monolithic

Often in monolithic service with many responsibilities, there might be interdependencies that make it difficult to make changes to your code. This is called technical debt. If you’re not able to make those changes quickly and effectively, that might lead to mistakes or might lead to certain vulnerabilities and make the two areas that need tremendous amounts of work defects.

---

Microservices

Modern architecture is often referred to as microservices. This is where we take those individual responsibilities and split them up into smaller servers or smaller pieces of architecture deployed across different of a stack. Now, you might have one server with a single responsibility. For example, we might have our API server, but also a calendar service or something like puppy directory. All of these systems are self-contained and minimal interaction between them is needed to accomplish our goals. If we needed to make a change to our API server, we don’t have to touch the other two.