> Just because you have a single program, it doesn't mean it is required to use a single database. I would challenge that. Obviously a well written "monolith"

> Just because you have a single program, it doesn't mean it is required to use a single database. I would challenge that. Obviously a well written "monolith" with well insulated modules, separation of concerns etc can use different databases but I heard too many times when I ask "why can't we shard the database" the answer "the data model is one and it's way easier to develop on one single data model that on N models inside the monolith".