Secure your Modular Monolith by pretending it's a cat
summary
Practical recipe for messaging security in a modular monolith: always attach user identity to messages, use the mediator pipeline or outbox to sign messages with private keys and to encrypt fields per-recipient so brokers and rogue subscribers can’t forge or read data. Handle token expiry by forwarding identity, embedding a hashed claim+body, or doing a token exchange for internal tokens. Use key management (KMS / HashiCorp Vault / Azure Key Vault) and dynamic short-lived credentials to rotate keys and limit impact when parts are scaled out.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 6:33Butterbean
- 7:21What is a modular monolith
- 12:12Adopting a cat
- 14:08How do users present credentials
- 17:12Authorization
- 18:23Commands Events
- 24:02Reading Messages
- 27:18Zero Trust Principle
- 29:14Hashik Vault
- 32:30Dynamic security credentials
- 34:03Personalization
- 36:31Partial Message Encryption
- 37:35Token Expiration
- 44:17Version Changes
- 47:59Summary
related talks
43mSecure your Modular Monolith by pretending it's a cat
40mSecure your Modular Monolith by pretending it's a cat
57mDistribu-ready with the Modular Monolith
29mSecuring your messaging networks: What needs protecting and how?
39mPrevent Phishing & Impersonation
59mMajestic Modular Monoliths
39mManaging Trust Between Multiple Clouds and Non-human Identities Without Passwords
43mModular Monoliths: The Architecture That Scales w Your Domain