Franck is a Developer Advocate for MongoDB. With 25 years of experience in database consulting for development and operations teams, Franck actively engages with conferences, writes articles, and participates in social media to continuously learn and share his knowledge. He is recognized as an Oracle Certified Master and an AWS Data Hero.
Relational databases were originally designed as the central hub for both data and business logic, shared by many applications through normalized schemas, strong integrity constraints, views, and stored procedures. This database‑centric model still works well for many systems. More recently, application‑centric architectures have become common. Autonomous teams build services, each owning a bounded context and often its own database. Business logic lives primarily in the application, where data first exists as domain objects and aggregates before being persisted. This shift, formalized by Domain‑Driven Design (DDD), changes how developers think about consistency, normalization, and duplication. PostgreSQL’s lightweight, extensible, and widely adopted nature makes it a possible choice for a database‑per‑service approach, typically accessed through ORMs and with relaxed relational constraints—for example, storing aggregates in JSONB. This session introduces key DDD concepts and the modern developer experience to help DBAs understand how developers design and evolve applications, with the goal of improving communication and collaboration between application and database teams.