It's a ready-to-use serverless back-end that generates a GraphQL API based on the developer's database schema. We've had developers building on 8base since October 2018. We've made refinements galore since. We'd love nothing more than honest feedback from the HN community!
Edit: I might use it if it had a freemium model not just trial. I often play w/ new technologies, forget about em, come back try em again and stick w/ the ones that stick in my mindshare, but a trial doesn't allow me that freedom -- at least for hobby projects.
A timed trial just feels weird. I like that Heroku, Netlify, Contentful, and Firebase have a free tier, so I can use it for small demos and to learn the platform. If I have to pay for every single tutorial or playground project I won‘t want to use the platform or even want to learn it.
It also kind of disincentivizes teachers on online platforms (like Udemy) to teach it. Because you often need to go through a few examples in order to learn something. i.e. if I do a node.js course, the course author isn’t just going to make me build 1 practice app, I’m probably gonna build a few and then host them on Heroku free dyno, the same way if I take a React course, I’m gonna build a few practice apps and host them on Netlify.
Even all the major cloud platforms have free tiers for this reason - to get devs hooked on their platform so there is no other option they'd rather use.
Not saying the free tier should be outrageous... maybe 100MB and 10k requests per month or something small like that.
I’m a product/frontend guy who’s trying to build a side project, and backend stuff has always been a PITA for me to figure out.
Right now I’m torn between investing time to learn AWS Amplify, or investing time to learn 8base.
8base has already captured my imagination, and I can’t wait to go further with learning it. Unfortunately I feel uncomfortable creating a few projects to practice and then later being shut out of them or be forced to pay $8/mth.
Another way to put it is that Hasura is mostly about enabling GraphQL on Postgres; 8base is the backend for powerful, enterprise-grade (when necessary) software. GraphQL is an essential design detail for us but not the business or product itself.
Regarding your comment about freemium; I've seen many backend products falter, pivot, and shut down from having unsustainable business models. We are offering a robust plan for $8 / month to start. If developers agree with us that their DX is better, then $8 shouldn't be an issue as their time is more costly. But we appreciate what you are saying and are watching this closely.
At the very least, offer a highly-limited and almost-crippled free tier, like Heroku or Glide does. Maybe you can only register a few users. Maybe the # of function calls are limited to a few a day. Or maybe dormant apps go to sleep.
I use 8base extensively and happy to see where it goes next and how developers adopt it
I'm using AWS and AppSync (The service for GraphQL) directly and managing infrastructure (other services) with AWS CDK.
I'm encouraging everyone to try AWS directly. The learning curve is a bit steeper but there will be no lock-in to a single service.
Now more and more services are offering a way to run serverless apps: Netlify, Zeit, 8base. It's nice and convenient, but knowing the source will let you design apps with proper security considerations.
The way I think of these things is always that the more tools you have in the tool-chest, the more things you can build. It's NEVER wrong to learn more or dive deeper. But just because you might know-how and be capable of building a house by sawing down your own lumber and smithing your own nails, doesn't mean you wouldn't want to order some parts pre-fab - or at least go to the hardware store!
To parent, you are gonna want to look at responsive web page information, most css templates and frameworks will be responsive but it is fairly simple to do from scratch now using stuff like flex box.
Best of luck to you guys!
As a side note... I'm working on some Gatsby projects and want to use 8base for the backend. The few tutorials I've seen so far seem to be loading data dynamically post-build versus creating static pages with data at build time. Do you have any examples of this yet?
Also, do you have an official Gatsby source plugin or are people generally using the generic "gatsby-source-graphql" plugin?
Great guy and super cool product from a company that is passionate about supporting the local developer and startup scene.
It's been a while since I looked into GraphQL backends, so I'd love to know how it is different compared to Postgraphile, Hasura or Prisma.