Tag
SaaS
← Clear filter
OperationsBus factor 1: when the cluster belongs to a single colleague
In many small teams, the cluster belongs to one colleague. That works fine until they go on vacation. Six steps to make sure operations no longer hinge on one person.
- Kubernetes
- SaaS
- Costs
SecurityNIS2 in Kubernetes operations: the evidence an auditor wants to see
NIS2 doesn’t require any particular technology, but measures and proof. For Kubernetes operations, that means personal access, a complete log and tested backups.
- Compliance
- Kubernetes
- SaaS
OperationsOne database per service: roles, privileges and the read-only user who sees nothing
The BI user has read access and still can’t see the new table. That’s not a bug, that’s PostgreSQL. And it’s the reason privileges have to be granted in a fixed order.
- Databases
- Scaleway
- SaaS
SecurityCustomer offboarding: why every drop needs a dump first
Deleting is easy, restoring is impossible. Offboarding needs a fixed order: back up, verify, then tear down. And a retention rule that someone has written down.
- Backups
- SaaS
- Databases
SecurityLet’s Encrypt rate limits: why SaaS subdomains need a wildcard certificate
Fifty certificates per domain per week sounds like a lot. Until the fiftieth customer gets stuck in onboarding and the certificate won’t arrive until next week.
- TLS
- SaaS
- Ingress
ArchitectureMulti-tenant SaaS: a namespace per customer or a row per customer?
Multi-tenancy is not a yes-or-no question. Most SaaS vendors need both: rows for the many small customers and namespaces for the few large ones.
- SaaS
- Multi-tenant
- Kubernetes