1. 22:15 28th Dec 2011

    Notes: 33

    Backend-as-a-service?

    As the list of *-as-a-service’s continues to grow, I thought I’d throw one into the mix. What about the idea of a backend-as-a-service (BaaS)?

    The recent surge of client side Javascript frameworks along with the attractiveness of simple RESTful APIs has created an environment where server-side interaction can be reduced to simply database interaction (including validation and some computation). But why stop there?

    What if the server-side of the equation was simply a RESTful, schema-less API? It could utilize MongoDB or some other document-oriented storage to avoid a strict schema definition, and even infer data relationships from the inbound URLs.

    For rapid prototyping, I think this would be amazing. Move your entire app development into the browser - just point Backbone.js or similar framework to the proper root URLs for their storage, and suddenly everything is down to client side HTML/CSS/JS.

    Obviously, this won’t work for everything. High performance applications may need to tune their backend for speed. Security would be a major concern as well, but could be managed similarly to Amazon’s S3 permissions, combined with authentication tokens sent on each request.

    The only other hiccup I see would session management. Traditionally, session management (and related issues like user authentication) are handled through the server side.

    But ultimately, a cookie-based session is simply a way of tying a particular user to a particular storage record for session data. If that cookie were replaced with a Javascript token, not much would change on a conceptual level.

    Ultimately, I think this would help developers produce faster while eliminating the need to hop back and forth across the increasingly obsolete divider between server and client side.

    Edit:

    I should mention - I realize Parse (and others) already have released a BaaS. But those focus largely on mobile deployments, and as far as I can tell, their primary value is in auto-generating model code and SDK’s to handle the REST calls. They don’t seem to offer anything for browser-based apps.

     
    1. lmjabreu reblogged this from davewasmer
    2. cdent answered: Although it doesn’t look like it on the surface, tiddlyweb and tiddlyspace are BaaS: tiddlyweb.com tiddlyspace.com
    3. g3niu5 reblogged this from davewasmer
    4. zvi answered: FWIW - I built and launched this last year - struc.to (prior to parse/kinvey/etc). The problem? Too small a market.
    5. singhshashank reblogged this from davewasmer
    6. yorapi answered: yup all BaaS should work at a basic level for the Web, however most are targettin the Mobile market. disclaimer as we are also seen as a BaaS
    7. ianmarkowitz answered: This already exists in some capacity, take a look at kinvey.com
    8. brianjesse answered: i’ve been working on BaaS at structal.org - expect to have a beta test in January
    9. davewasmer posted this