@Katherine_Duh There is a straight-forward common thread in all the use cases. The vast majority of use cases I’m reading here have to do with data normalization and reuse of functionality. People don’t want to duplicate the same data and features across different bases.
It’s pretty simple, IMO:
- If I have a list of people, I don’t want to recreate my CRM functionality across multiple bases and have duplication.
- If I have a list of products, I don’t want to recreate my entire product-catalog functionality across multiple bases and have duplication.
Most relational databases allow you to link across databases, and some even allow you to link across database servers. This may be restricted to virtual views, read-only access, or whatever. But it is an essential feature when working with complex database, which I’m sure most of your customers evolve into over time.
I haven’t read every post here, but reading several of the recent posts, it seems like an update on your considerations and status on this would be greatly appreciated.