Live data from Hacker News

Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

8base.com

51–60 of 80 posts

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#51
post #2

Albert from 8base here: Between my last two companies, we raised over 100-million in VC capital that all got spent on hiring massive engineering and sales teams. I always had this dream about starting up a company that could grow exponentially with an agile team, relying on a self-service product that was so awesome it sold itself. And, that it would simplify software development for developers and businesses who rel…

I'm curious why pay for your product, when I could just use Hasura for free + the instance it's running on?

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.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#52

Earlier quoted context omitted.

I'd try logging in and creating a data-model for your project. All the GraphQL operations will be generated from that so you can start using the workspace API. Whatever application you're building than then connect through there. https://docs.8base.com https://youtube.com/c/8base

How does a graphql API help with building a responsive web page? 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.

Lol. I totally misinterpreted your question. Answer: Webflow.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#53
post #17

Congrats for shipping, looks great. 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.

Thanks Dakna! I'd say that Prisma and Postgraphile both fall more into the data access layer category where you'd use them instead of other ORMs (like Sequelize). 8base and Hasura are more similar, though Hasura is focused on layering over a person's Postgres database without providing any resolvers while 8base is a fully-fledged backend-as-a-service. Like Parse for GraphQL in 2019.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#54

Go go 8base team! I met them at GraphQL Berlin and was really impressed by their product. Fills an important hole in the JAMstack ecosystem.

Thanks Evan. Great to hear from you and appreciate the kind words! We need to talk at some point about integrating Fauna into 8base.

Yes we do! :-)

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#55
post #17

Congrats for shipping, looks great. 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.

Thanks Dakna! I'd say that Prisma and Postgraphile both fall more into the data access layer category where you'd use them instead of other ORMs (like Sequelize). 8base and Hasura are more similar, though Hasura is focused on layering over a person's Postgres database without providing any resolvers while 8base is a fully-fledged backend-as-a-service. Like Parse for GraphQL in 2019.

PostGraphile is not an ORM, it’s a client-facing GraphQL API designed to be consumed directly from your frontend applications (web apps, mobile apps, etc). This is why it has such powerful customisation and extension features so you can use it to build the GraphQL API you want.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#56
I recently switched our startup to 8base due to its ease of use, user-friendly UI, and minimal set-up. Their backend dashboard is amazing — our customer support staff will have no issue looking up and modifying any data or creating new data. Highly recommend 8base.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#57

I recently switched our startup to 8base due to its ease of use, user-friendly UI, and minimal set-up. Their backend dashboard is amazing — our customer support staff will have no issue looking up and modifying any data or creating new data. Highly recommend 8base.

Thanks, heymartinadams, really appreciate the comments. May I ask what you were using or planning to use before you made the switch?

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#58

Earlier quoted context omitted.

Thanks Dakna! I'd say that Prisma and Postgraphile both fall more into the data access layer category where you'd use them instead of other ORMs (like Sequelize). 8base and Hasura are more similar, though Hasura is focused on layering over a person's Postgres database without providing any resolvers while 8base is a fully-fledged backend-as-a-service. Like Parse for GraphQL in 2019.

PostGraphile is not an ORM, it’s a client-facing GraphQL API designed to be consumed directly from your frontend applications (web apps, mobile apps, etc). This is why it has such powerful customisation and extension features so you can use it to build the GraphQL API you want.

Benjie, I appreciate you chiming in here personally. Apologies if I oversimplified as I am not all that familiar with your product. Aside from looking at the nuances of the GraphQL engines of either product, the primary difference is that 8base is hosted and ready-to-use and PostGraphile is for someone who wants to build, deploy and manage a server application and is using Postgres. Aside from that, there are likely lots of other differences.

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#59

Earlier quoted context omitted.

PostGraphile is not an ORM, it’s a client-facing GraphQL API designed to be consumed directly from your frontend applications (web apps, mobile apps, etc). This is why it has such powerful customisation and extension features so you can use it to build the GraphQL API you want.

Benjie, I appreciate you chiming in here personally. Apologies if I oversimplified as I am not all that familiar with your product. Aside from looking at the nuances of the GraphQL engines of either product, the primary difference is that 8base is hosted and ready-to-use and PostGraphile is for someone who wants to build, deploy and manage a server application and is using Postgres. Aside from that, there are likely…

No problem; I saw 8base at one of the GraphQL conferences, looks cool. I agree: PostGraphile is intended for people who want to control their own servers (be that via serverless, containers, Heroku, or traditional servers).

Re: Show HN: 8base – Ready-to-Rock GraphQL API and Serverless Back End

#60

Super stoked to see 8base out here. I love JAMstack and I love how 8base fills up the data layer for my JAMstack projects nicely. You will know what I am talking about if you have spent days trying to setup a GraphQL backend for JAMstack project. I wrote about how I use 8base for JAMstack on CSS Tricks few months ago https://css-tricks.com/hey-lets-create-a-functional-calendar... . I use 8base extensively and happy t…

Easily helps with API integration challenges thru the GraphQL layer. For example, using a simple endpoint I can translate an image with a text overlay (constructed using a Cloudinary API) from English to any language (I'm in Spain at a conference now, so it's gotta be Spanish) like: Input: https://res.cloudinary.com/demo/image/upload/w_500/l_text:Ar... Output: https://res.cloudinary.com/demo/image/upload/w_500/l_text:Ar...
Post reply on HN