Why?
We consistently find that everyone has lots of sources of truth. You know, CRM holding customer data, accounting systems handling invoices, and more scattered across different SaaS platforms and databases? It's a real pain to sync it all up!
In the past we used to copy data from everywhere to the DB, but that always breaks at some point.
Well, after years of grappling with this issue, we wanted a way to easily build a single GraphQL API in front of all those sources. An API that allows you to execute queries that even span across datasources (give me DB records where customer in CRM name is "Bob"), and also allows you to administer your data all from one place.
That's why we built Graphweaver. We've been using it on our projects for about a year now and think you'll love it too!
Features
📝 Code-first GraphQL API: Save time and code efficiently with our code-first approach.
🚀 Built for Node in Typescript: The power of Typescript combined with the flexibility of Node.js.
🔗 Connect to Multiple Datasources: Seamlessly integrate Postgres, MySql, Sqlite, REST, and more.
🎯 Instant GraphQL API: Get your API up and running quickly with automatic queries and mutations.
🔄 One Command Import: Easily import an existing database with a simple command-line tool.
Comments and Reviews
I love Graphweaver because I can keep my data where it lives, but build applications across all of it. It's so common that we end up with 6 SaaS platforms and a database in the middle. Graphweaver is the best way I've found to build applications on top of all of that.
I like Graphweaver because it lets me filter data in one database by data in another source. i.e. I can filter the data in my PostgreSQL database by data in the CMS (e.g. Contentful) and/or by data in MailChimp or SalesForce without having to copy data across or host a lambda like you have to do if you use Hasura to do the same thing.