Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.
When you have a bunch of microservices, this is something that has to be considered.
Implement it once or in every microservice, or something in between?
Vadim Bauer Vad1mo
Vad1mo
/ docker-private-registries
Last active
July 19, 2017 06:19
— forked from salex89/docker-private-registries
List of private docker repositories (self-hosted and SaaS) other than Docker Hub
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Portus - http://port.us.org/ | |
| Quay - https://quay.io/ | |
| Harbor - https://vmware.github.io/harbor/ | |
| Atomic Registry - http://www.projectatomic.io/registry/ | |
| Nexus Repository Manager OSS 3.xx - https://www.sonatype.com/nexus-repository-oss | |
| "Official" Docker Registry 2.0 - https://docs.docker.com/registry/ | |
| "Registry For Enterprises" - https://private-docker-registry.com/ |
Vad1mo
/ README.md
Created
April 13, 2017 20:23
— forked from omidraha/README.md
Authentication and Authorization Concepts for MicroServices