Foreign Keys Between Modules in a Modular Monolith: Keep, Restrict, or Drop?

Disclosure: I build Schemity, a desktop ERD tool - this post is from our blog and uses it for the examples. TL;DR: Keep a foreign key between two modules while they share one database and ship together: it costs an index and a row lock, and the coupling it creates is the coupling your code already has. Change its delete action to RESTRICT so no... Weiterlesen: Foreign Keys Between Modules in a Modular Monolith: Keep, Restrict, o…