# Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication

DevFeed: [Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication](<https://devfeed.tech/articles/article-identity-as-an-architectural-concern-enterprise-iam-beyond-authentication-120951.md>)

Original publisher: [Read original article](<https://www.infoq.com/articles/identity-as-architecture/>)

Author: Vaishnavi Khosla

Published: 2026-11-06T09:00:00Z

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [article](<https://devfeed.tech/tags/article.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [based](<https://devfeed.tech/tags/based.md>), [data](<https://devfeed.tech/tags/data.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [event](<https://devfeed.tech/tags/event.md>), [experience](<https://devfeed.tech/tags/experience.md>), [governance](<https://devfeed.tech/tags/governance.md>), [graph](<https://devfeed.tech/tags/graph.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-as-architecture](<https://devfeed.tech/tags/identity-as-architecture.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [java](<https://devfeed.tech/tags/java.md>), [management](<https://devfeed.tech/tags/management.md>), [models](<https://devfeed.tech/tags/models.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [scope](<https://devfeed.tech/tags/scope.md>), [security](<https://devfeed.tech/tags/security.md>), [service](<https://devfeed.tech/tags/service.md>), [single-sign-on](<https://devfeed.tech/tags/single-sign-on.md>), [stream](<https://devfeed.tech/tags/stream.md>)

## AI overview

At enterprise scale, identity design shapes data models, service boundaries, ownership governance, and revocation behavior. The author describes modeling ownership and time-bounded access as relationships in Neo4j, queried through GraphQL; this made common ownership and validity questions direct, though it adds datastore and modeling costs, and the article says flat RBAC remains suitable for small, single-app setups. A unified workflow for attestation, credential rotation, and vaulting reduced reported revocation time from about three days to under one. Because the vault is owned by another team, the integration fails closed and reconciles its state before marking vaulting complete. Across services, scoped OAuth 2.0 token exchange carries identity context while a policy decision point makes authorization decisions. Kafka distributes entitlement changes, so revocation is eventually consistent: consumers invalidate cached decisions, and a maximum cache age bounds stale access if an event is lost, at the cost of more source-of-truth checks when that limit is shorter.

## Source excerpt

The way you design your identities will drive your data models, your service scope, and your revocation policies; enterprise identity management is thus an architectural problem, not an afterthought. Based on our experience in service account governance, this article touches upon graph vs. RBAC, integrating a vault you don't own, and bounding revocation latency for an event stream. By Vaishnavi Khosla