You can manage up to 0 partners easily. Once you go above that threshold, you're into "2-Generals" territory. At that point you're either inconsistent, eventually-consistent, or you're just bypassing your own database and using theirs directly.
> dev and user experience are going to be much simpler and easier.
I have objects, not relations. I'm not going to do the work of un-nesting a fat json transaction to store it in a single relation (or worse, normalise it into rows across multiple tables).
SQL now (for dev experience) && no-SQL later (for scaling)
to: no-SQL initially (for *much better* dev experience) && no-SQL later (for scaling)
I can get behind that.> When your objects are inconsistently shaped something has to fix them
They have one schema (the class file) instead of two (the class file and the SQL migrations).
But what happens when that schema defining class file needs to change? You put all your migration code there? How is that different from SQL migrations?
You can get really far with a RDMS before event sourcing etc is needed, the benefit being both your dev and user experience are going to be much simpler and easier.
If you already know your problem domain and scaling concerns up front sure. But starting with a scalable pattern like this is a premature optimization otherwise and will just slow you down.