CloudMine Another Step Closer to Replacing Developers

It wasn’t that long ago, just late last year, that I started wondering if CloudMine was trying to replace me. Just a few months pass, and it seems my fears were not unfounded.

If you’re not familiar with what the CloudMine API offers, it’s backend-as-a-service, with the core feature being easy storage and access of user - and global - data. All that’s required to store JSON data in the global scope is an HTTP call with the application’s credentials. Storing user data in a private scope only requires the addition of the user’s credentials.

It’s worth noting that mobile developers aren’t the only ones using CloudMine. It’s also a dead simple database replacement for some web applications. I’ve put together a simple wrapper for the Zend Framework that not only provides access to storing and retrieving data, but also acts as a Zend_Auth adapter, offloading Authentication to CloudMine as well. Other developers are using CloudMine as storage for specific use cases, for example, tracking page views.

CloudMine started rolling out features right after the public launch - the first was the ability to run server-side javascript. The core features provide simple, query-able, storage. Adding server-side custom code allows various data manipulation and 3rd party Integration to be moved from the mobile device (or whatever your Platform) to CloudMine.

Data from the client platform can be processed as it’s stored. For example, a social application may allow users to connect a post to a tweet, and after storing the tweet’s id, CloudMine could Fetch the relevant data from Twitter and store that as well.

Custom code can also process data as it’s requested. In those cases CloudMine returns the requested data and the results of the executed code. Perhaps a communication application allows you to send emails, and when returning the message data, CoudMine could also pull delivery data from SendGrid.

Keeping the features rolling, CloudMine recently added the ability to use the service as an Endpoint for HTTP callbacks - the kind of callbacks used by services like SendGrid when an email is sent to your account, or Nexmo when an SMS is sent to your account.

Adding support for server-side code allowed CloudMine to interact with 3rd party APIs by making HTTP requests, now this new feature allows 3rd party APIs to interact with CloudMine, making the platform that much more usable to developers.

If you’re looking for a bit deeper look at what can now be built, wander over to the CloudMine blog, and checkout the example SMS responder using Nexmo, and geofencing using UrbanAirship.

And if you want an excuse to build something yourself, CloudMine and Nexmo are running a contest that ends this weekend (currently I’m a part-time developer evangelist with Nexmo).

I’m still not sure if the goal of CloudMine is to replace me, but for now, CloudMine’s growing feature set sure makes building applications on their platform even easier. So if you’re looking for a contract web developer CloudMine developer, let me know.

Be sure to read the next Mobile article: 307 Mobile APIs: Foursquare, Instagram and iTunes