Flipkart Marketplace Platform · View 08 of 25 · 3 · Structure
Decisions
- One AKS fleet with four tenancies; only the cardholder data environment is a separate cluster in a separate subscription
- Java 21 for commerce and money, Go for the high-QPS edge and inventory, Python only where a model is being served
- Every service owns its schema — there is no shared database and no cross-service SQL
Why the PCI plane is split
- A separate subscription bounds the audit: nothing else inherits the scope, and the RBAC boundary is a tenancy boundary
- No card number leaves the token vault; the commerce plane holds tokens and amounts only
- The cost is a second cluster and a cross-plane mTLS hop on the checkout path, and it is worth it
Deliberately omitted
- Sidecars, service accounts and network policies — implied by Istio ambient mesh, not drawn
- The observability stack, which has its own view
- Most edges: nine are drawn out of roughly ninety, chosen to show each boundary crossing once
