4 ms·
What's the backwards compatibility/breakage story? I think that's a critical question for any tool that wants to be the go to place for this kind of task. It ha
by hyperpape 7y ago
What's the backwards compatibility/breakage story? I think that's a critical question for any tool that wants to be the go to place for this kind of task. It has to be the kind of project you can run for years, making small changes to, and still be secure/deployable/upgradable.
- gavinray 7y agoHasura allows you to use a pre-existing Postgres database as its source. Alternatively, you can either build a schema from scratch in SQL, with some other tool, or use Hasuras web console which has a visual schema-building and relationship-building UI. The team takes pretty good care of upholding backwards compatibility -- as it stands, most of the new features they have been working on are niceties outside of the scope of basic CRUD functionality and permissions/authorization (which they have pretty much nailed at this point). Hasura Engine instances are versioned, and if you like, you could also opt to just never upgrade.
- hyperpape 7y agoThanks, but isn't that just the backend/API? I should've stated this, but what really triggered the comment was the React frontend. There's a lot of churn in the JS/React world.
- cpursley 7y agoReact Admin has the concept of data providers which can be swapped out. https://marmelab.com/react-admin/DataProviders.html#available-providers https://marmelab.com/react-admin/DataProviders.html#availabl... So for example, you could start with Hasura back end (GraphQL) and later swap to a custom JSON API without changes to the UI code. As for the react-admin framework, it's been around for a while and has regular frequent.