|
|
|
|
|
by cainlevy
3151 days ago
|
|
Yep, it's very broad. Let's say it depends how "majestic" a person's monolith is? :D One point of context I'd like to inject here is that chatter between AuthN and a host app is pretty minimal. Aside from executing admin actions like locking an account, the main dependency is fetching a public key to verify JWTs. This public key can be cached using a standard key fingerprint, which means it only needs to happen once per process. Architecture does matter, and I've been pretty happy with how AuthN's boundary has played out. |
|