Publish events from your Spark Core
blog.spark.io
blog.spark.io
Sadly, I'm not just being ironic.
I recently was told that a product would be hosted on a local cloud.
What they meant was an NFS share.
* On-demand self service
* Broad network access
* Resource pooling
* Rapid elasticity
* Measured service
If EC2/AWS doesn't meet that definition, what does?[1] http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145...
What if I don't want to connect through the Cloud?
That's okay! The Cloud is there to make the Core easier to work with, but if you'd rather do it yourself, that's no problem. The Core lets you do your own socket programming over TCP and UDP.
If you want the simplicity of the Cloud but you want it on your own server, we'll be releasing an open source version of the Cloud designed for quick and easy deployment.
The reason I asked is that once they get purchased by, say, Google or Facebook, their cloud services will probably get either shut down, or severely constrained. I'm not interested in sinking resources into a platform based on question marks.
> The Core lets you do your own socket programming over TCP and UDP.
There's nothing stopping you from writing your own TCP/UDP listener server and having the Spark write to a port on that.
We will definitely be releasing this, we consider it a promise we made to our Kickstarter backers.
We'll probably do a small beta as we get the local cloud ready for release to make sure things are easy to use and work as expected. Since it'll be open source, I'm hoping the beta group can help find bugs and even send in pull requests if there are pieces they want added. The beta signup thread is here at the moment: https://community.spark.io/t/where-is-the-source-code-for-th...
Thanks, David
Also, re the spark:
"No need to ever plug the Core into your computer" vs. "Power it over USB"
Edit: scratch that, https://www.spark.io/# has details of a "battery shield" with a LiPo - an idea of the battery life when running the OP's sensor application would be nice though?