I work at Hasura (disclaimer, not to self-promote) and of the user questions I've seen being fielded recently, this has been maybe one of the fastest-growing.
It's typically something like "My org $BIGCO has data in multiple places/databases, and teams have fragmented services they've set up for access with no consistent API or central hub for all of this."
And they are interested in a sort of data-aggregator/central-access point for the data stored in databases of varying dialects + merging their API's into a unified service. Sometimes they also want to (transparently) join/map data across sources too.
I think this space is likely going to become more prevalent just by the nature of both organizational growth and inevitable tech debt.
It's an interesting domain and problem, that's for sure.
It's typically something like "My org $BIGCO has data in multiple places/databases, and teams have fragmented services they've set up for access with no consistent API or central hub for all of this."
And they are interested in a sort of data-aggregator/central-access point for the data stored in databases of varying dialects + merging their API's into a unified service. Sometimes they also want to (transparently) join/map data across sources too.
I think this space is likely going to become more prevalent just by the nature of both organizational growth and inevitable tech debt.
It's an interesting domain and problem, that's for sure.