Comments by "" (@adambickford8720) on "The Thing No One Tells You About Microservices" video.

@stephendgreen1502 correct, there are definitely 'cross cutting' concerns that don't work in full autonomy. Security is one of the cases. There are others. For example, you likely should all be using some kind of standard for tracing/logging or trying to troubleshoot a request across services will be near impossible. If you have many disparate systems to monitor app health, that can be an issue too. this is usually where some kind of 'platform engineering' comes into play. the systems have to be coupled to work, the challenge is doing the minimal amount.
2
Usually that's where some kind of standard comes in. For example, all services will have to support the same JWT IDP (or something federated) to authenticate so each service can handle authorization.
1
@stephendgreen1502 autonomous doesn't mean anarchy. You're still obligated to support the apis you publish. That why companies agree on standards as the lowest common denominator. If you agree on open api, it doesn't matter what language or framework you use, but yes, you need to support open api. Its no different than supporting HTTP.
1