Live data from Hacker News

Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service

news.ycombinator.com

11–20 of 95 posts

Re: Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service

#14

I just don't believe in the 1 backend to rule them all approach. Services like Stripe, Algolia, Datadog, Pusher, Mapbox, Imgix etc all make a lot of sense. It's easy to plug them in to your existing backend and extend your app's functionality. Using someone else's backend for your app is a terrible decision though, the lock-in is just too large. For this to succeed they'll need to add a lower level interface to the m…

Hey that is great feedback! To address your point about the lower level interface, as part of today's launch we released our Logic features that lets you do exactly this. The new features allow you to add compositions of custom microservices to any mutations in your Scaphold API. For example, assume you were building Slack and you were setting up the createUser onboarding flow. A new user might be invited to Slack and to join a specific team.

In a real app you would want to first validate the email, then make sure the user has permission to join the team, then persist the object to the database, then using the generated ID create an M-M association with the team and maybe even asynchronously send push notifications to all the other users in the team. Flows like this are why we built Logic. You can host your business logic anywhere and Scaphold essentially acts as a runtime for your microservices.

This new feature is particularly powerful so I'd be happy to discuss it more in depth if you'd like.

Re: Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service

#15

Congrats on the launch, the new website looks really nice! I think the focus on integrating with a variety of services really plays to the strengths of GraphQL, and addresses some of the concerns people usually have with backend as a service platforms!

Thanks for the support! Agree with your sentiment, we talked to many users about how best they like to extend their API, and found that the modular approach was best for popular services like Stripe, Auth0, and so on. And for the rest of the custom workflows, we've provided the ability to extend your API with your own custom logic through synchronous and asynchronous hooks that can call out to any web service that you may have hosted anywhere, whether it be on AWS Lambda, Azure Functions, Webtask, or even self-hosted. If you're in the portal, you can check it out under the "Logic" tab.

Re: Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service

#18
post #11

This looks really interesting. Thanks for sharing! I checked out the Projects page, but they look mostly like tutorial or hackathon types - is anyone running scaffold.io in production?

Hey! Yes we have an number of larger production apps on the platform. We actually power 4 National Geographic domains in Europe as well as some cool new startups like http://cheddr.com/. We are working on getting more in depth customer profiles that will go on the community page soon!

Re: Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service

#19
post #13

I think the "Customer stories" section needs to be updated. The bio picture and link for the Nat Geo reference points to Bonnier.

Thanks for the feedback. We didn't want to be misleading though since we actually run several of Nat Geo's domains in Europe through Bonnier. They own the licenses to them in that particular region. Here's a piece that explains their relationship: http://en.bonnierpublications.com/national-geographic-0
Post reply on HN