React, Flux, GraphQL, Hack, HHVM...? All of this and more!
The logic and complexity of web applications has largely transferred to clients. Still you need a backend to persist your data, do validation and so on. Reindex a new entry to the BaaS market, but it has embraced GraphQL from the beginning.
There are large companies like Google riding the Backend as a Service wave with the recent acquisition of Firebase. Compared to that Reindex is a small fish in the sea, but the focus on GraphQL gives the company an edge due to the universal nature of this high level transfer protocol.
As a standard GraphQL is more defined than REST, which allows users to get up and running with expected results. This gives GraphQL advantage over vendor specific REST APIs. The Reindex service offers a number of paid options as well as free accounts for development.
Developers wanting to develop rich interfaces with a persistent data storage can still roll their own backends, but many times at least in the prototyping phase this is something that is secondary. For this kind of scenarios using Reindex and GraphQL can reduce waste as you can choose to standardise your communications to GraphQL.
Reindex is rooted around the React.js ecosystem. Even if their tagline is about "Instant GraphQL Backend for Your React Apps", you're not tied to it. You can choose to use Relay with React or Angular 2 and Apollo you can have a defined method for backend queries and mutations from day one.
Later on if you need more than the Reindex service can offer, you can move to other platforms supporting GraphQL or something like PostGraphQL for directly linking up to a robust relational database. All while keeping your client example started on the Reindex starter kit for React as the backbone of your client application. GraphQL enables that freedom.Tweet