There are no major reporting engines that support GUN (nor most NoSQL DB systems). My solution for this kind of issue is to:
Architect the NoSQL database, treating each collection like a table, with only a single tier deep of records; AND
Have a general software system that subscribes to each collection, and inserts/updates records in a relational database.
I'm sure many coders can repeat [2], and do it in all kinds of mind-bending ways. But ideally, each NoSQL vendor does this kind of thing once and well. I'm sure there are unique features with each NoSQL database system to ensure the integrity and timeliness of relational reporting data.
(Also, there's a chance to use a streaming SQL language so that special reporting results tables can be built live, and aggregate results can be maintained for ready near-instant access.)
This might be a key feature that's missing to enable widespread adoption. With an adaptor to a relational database, most reporting engines will be able to READ from such relational databases for business reporting needs { Dashboards, Emailed PDF reports, adhoc reporting, etc }
It would be best if a "GUN-PostgreSQL" (for example) adaptor project could be managed alongside the core GUN project(s).
Benefits:
Backups - there are standard mature practices and tools for backups
Technology-redundancy - Gun-db is solid, but not near as mature and trusted yet as postgresql. Being able to have data in postgresql as well means more peace of mind.
Leverage postegresql - only implement features in gun-db that you can't workaround with postgresql. That means you can focus on the biggest benefits of gun-db first.
SQL - one of the leveraged benefits - SQL query directly off postgresql, don't try to parse SQL with gun
GraphQL - another leveraged benefit. With Postgraphile you can turn postgreql into a graphql server leveraging views, and the security model.
Reporting tools - unlock tools like powerbi
(If you think of any more benefits please comment, and I'll add them to the OP list here)
amark
commented
5 years ago
Feature request.
There are no major reporting engines that support GUN (nor most NoSQL DB systems). My solution for this kind of issue is to:
I'm sure many coders can repeat [2], and do it in all kinds of mind-bending ways. But ideally, each NoSQL vendor does this kind of thing once and well. I'm sure there are unique features with each NoSQL database system to ensure the integrity and timeliness of relational reporting data.
(Also, there's a chance to use a streaming SQL language so that special reporting results tables can be built live, and aggregate results can be maintained for ready near-instant access.)
This might be a key feature that's missing to enable widespread adoption. With an adaptor to a relational database, most reporting engines will be able to READ from such relational databases for business reporting needs { Dashboards, Emailed PDF reports, adhoc reporting, etc }
It would be best if a "GUN-PostgreSQL" (for example) adaptor project could be managed alongside the core GUN project(s).
Benefits:
(If you think of any more benefits please comment, and I'll add them to the OP list here)
Thanks.