First impressions: very little magics/transparent, reasonable pieces, reasonable architecture, well packaged, nicely automated, descriptive UI, no glaring wtfs, all the bases are covered, looks easy enough to customize at any layer with skills I already have — all very sensible.
Damn.
Transparency: I felt like it wouldn't be hard to figure out what was going on behind each step. First guess easy vs black box not-so-fun.
Overall easy to grok created app plus Hasura meta data associations and transformation points.
Agreed that built in ACLs and Baas is really fantastic.
* for the host-your-own version are there any HA features for Postgres?
* what language is it written in? GitHub link?
Not right now. This is definitely on our roadmap though.
> what language is it written in? GitHub link?
It's mostly in Haskell, with smatterings of Python. Planning to open source it soon!
I ask because I'm currently using LB for a project and while I actually like it a lot I always like to be aware of alternatives and similar tools that I might need in the future.
Key value-prop differences are that out-of-box APIs are just one part of Hasura. The idea is to make it easy to integrate with community services (containerised) or deploy your own services in whatever language/stack.
Some other specific differences:
1. Hasura Data API is a graphql like query language to Postgres.
2. Deployment is similar to Heroku. So you deploy code in any language/framework
3. Nginx based API gateway behaves like a session middleware, so that any upstrea service can re-use auth
One minor nit: It is quite nice that you provide links to jump to the right place for each step, but I would suggest adding images of the equivalent spot to click in the UI.
So, what's the registration code?
Thanks ! Alas, Tanmai (our CTO) will quote this at us for the foreseeable future, this being his idea.
> So, what's the registration code?
This is just something that is used with the startups and incubators we partner with. You can ignore this.
The logo is by https://twitter.com/shmunday Cartoons by http://www.sandhyaprabhat.com/
Key features:
1. Data APIs on a Postgres database
2. Deploy with git-push, or any docker image
3. Expose HTTP services on the API gateway over subdomains/paths
4. Automatic LetsEncrypt SSL cert generation for exposed http services
5. SSH service to get tunnelled access to TCP services on your cluster
6. Auth middleware built into the API gateway, so that upstream services don't have to resolve sessions
7. Out of the box auth APIs for password, email, recaptcha, social login. mobile-OTP stuff