51–60 of 95 posts
What databases are supported - like can I use oracle database with Scaphold.
Is there support for websockets.
Why Scaphold ? I see there are many companies in this space since last few years - what unique selling points will help a customer choose Scaphold.
Dont you think rise of PaaS will make BaaS redundant easily going ahead. Since BaaS is now a very small layer on top of PaaS.
Big fan of what you are doing! But can you elaborate a bit on TAM? Isn't the possible market too small? https://github.com/coffeemug/defstartup/blob/master/_posts/2...
At a glance it does sound like a very small potential market which makes me curious as to why YC would fund them. Perhaps there's a belief that the market will grow as these tools lower the barriers to entry (facilitated by GraphQL) for building applications?
We’ve tried all available GraphQL BaaS and now use Graphcool which doesn’t have all the features Scaphold provides but the ones they have are very stable and mature. Also their API seemed by far the best one we’ve tried yet (e.g. they are providing an extra endpoint for Apollo client).
Have been trying BaaS lately - few questions. What databases are supported - like can I use oracle database with Scaphold. Is there support for websockets. Why Scaphold ? I see there are many companies in this space since last few years - what unique selling points will help a customer choose Scaphold. Dont you think rise of PaaS will make BaaS redundant easily going ahead. Since BaaS is now a very small layer on top…
1) You currently can't use Oracle DB with Scaphold. We have a hosted database that comes along with each app right from the get-go.
2) There is support for websockets through GraphQL Subscriptions. Each new type that you create in your schema will expose the ability to subscribe to events of that type.
3) There are a bunch of PaaS services that exist out there, but the speed at which you build apps on Scaphold is undoubtedly faster. We give you the ability to think about your data in a modular way by appending large pieces of functionality to your app without having to write any server-side code. But you also get the flexibility to bind your custom logic to the same API through your own hosted microservices. Out of any BaaS platform on the market, we provide the most feature-rich platform that can actually help you launch into production and scale to large workflows. So far we already have a few large customers aboard and growing fast.
If you're interested to hear more about our feature set, I'd love to chat with you more directly about your specific use cases and see how we can address those. Feel free to join our Slack and PM me directly (http://slack.scaphold.io). I'm @vince
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…
Our mission is to make software development like playing with Lego. You're combining existing services like Stripe, Algolia (...) to quickly build your own applications. GraphQL is the common denominator between all these components and provides an incredible developer experience.
On a more general note what distinguishes Graphcool from other services: We're optimizing for the best possible developer experience (DX) while maximizing the degrees of freedom what's possible to build with Graphcool.
I don't think it's in very good taste to promote your thing in someone else's launch thread.
We detached this comment from https://news.ycombinator.com/item?id=13474424 and marked it off-topic.
Earlier quoted context omitted.
Yes, it's something we're trying out for YC W17. https://news.ycombinator.com/item?id=13366964 was the first one, and this is the second one, so far.
So, it's preferential access to the front page in the same way as YC job ads, but no special comment moderation?
They'll still have voting and commenting like regular stories.
Edit (2020): in the end, I didn't get around to writing that code and users didn't turn out to mind the occasional case where a launch ad and a job ad are on the front page at the same time. If it becomes an issue at some point, we can still implement that bit.
Earlier quoted context omitted.
So, it's preferential access to the front page in the same way as YC job ads, but no special comment moderation?
Yes, assuming I'm reading you correctly. We'll make it so there isn't a launch post and a job ad on the front page at the same time, once I get time to write some code—that way there won't be any more slots reserved for YC than before (i.e. one at a time). Since launches are more broadly interesting than job ads, this feels like a win-win. They'll still have voting and commenting like regular stories. Edit (2020): in…
If you code while working for another company dont they own that IP? Unless specifically stated on your employment contract? Just curious! Thanks
not if you code outside of working hours with your own equipment