Live data from Hacker News

Show HN: Simperium, a realtime data layer

simperium.com

11–20 of 90 posts

Re: Show HN: Simperium, a realtime data layer

#12
post #10

This one is the best so far: 1. Works with any JavaScript library 2. You can write server-side logic 3. Operational Transformation baked in Seriously I cannot find anything bad about this project. (I really wanted to.) My questions: 1. Is the server side written in Python? 2. Is there offline support for JavaScript apps too? (I tried this with my own library and I think it was a wrong direction -- it only made it mor…

1. Server side is all python (combination of tornado/gevent/zeromq)

2. We've experimented with it, we'll likely add it as an option in the future since there may be security concerns depending on the app.

Re: Show HN: Simperium, a realtime data layer

#13
post #12
post #10

This one is the best so far: 1. Works with any JavaScript library 2. You can write server-side logic 3. Operational Transformation baked in Seriously I cannot find anything bad about this project. (I really wanted to.) My questions: 1. Is the server side written in Python? 2. Is there offline support for JavaScript apps too? (I tried this with my own library and I think it was a wrong direction -- it only made it mor…

1. Server side is all python (combination of tornado/gevent/zeromq) 2. We've experimented with it, we'll likely add it as an option in the future since there may be security concerns depending on the app.

Thanks! Can you please tell me something about the number 3. Sorry just edited it!

Re: Show HN: Simperium, a realtime data layer

#14
post #10

This one is the best so far: 1. Works with any JavaScript library 2. You can write server-side logic 3. Operational Transformation baked in Seriously I cannot find anything bad about this project. (I really wanted to.) My questions: 1. Is the server side written in Python? 2. Is there offline support for JavaScript apps too? (I tried this with my own library and I think it was a wrong direction -- it only made it mor…

I'll take number 3. Core Data one-to-many relationships are indeed handled automatically. On the JavaScript side, you'll see these relationships reflected in both directions using unique identifiers, but you need to interpret them accordingly. This is pretty straightforward using collections in libraries like Backbone.js.

Re: Show HN: Simperium, a realtime data layer

#15
We desperately need a high quality open-source Firebase/Simperium/Spire. A simple, robust, realtime data synchronization layer with libraries for major platforms. These projects all look great, but outsourcing this infrastructure is simply not feasible for lots of projects.

Re: Show HN: Simperium, a realtime data layer

#17
post #6

Simperium dev here. We're launching our beta to gather feedback. Let us know what you think.

Jaw-dropping. Perhaps it's too late to predict that 2012 will be the year of realtime interaction, but between this, Meteor, Firebase, etc., not only are all the tools converging in that direction, but they all appear to be drop-dead easy to use. Thank you for this. Is there an IRC channel or Google Group for questions?

Don't forget about https://github.com/socketstream/socketstream which expects 0.3 to be dropped later this month. Very extensible.

Re: Show HN: Simperium, a realtime data layer

#18
"With Simperium, you own your data - that's important!"

Not to take away from some of the great projects featured on HN recently, but statements by Simperium like this make me much happier as a developer and business owner: "We believe the best apps have both a great user experience and unique backend services.".

From https://simperium.com/overview/: It is not a backend-as-a-service. We believe the best apps have both a great user experience and unique backend services. Our focus is to provide a great data layer between your frontend and backend while integrating with other providers of tools, hosting, and services.

Re: Show HN: Simperium, a realtime data layer

#20
post #16

This almost seems unreal. What kind of latency would you be dealing with when your application(s) deal with many concurrent connections? For example, say a cross-platform multiplayer game with a persistent, shared world?

Latency is good right now (low hundreds or less), but for launch we focused on data integrity and reliability.

That leaves room for improvement, including some low hanging fruit like eventually giving you the ability to disable versioning for certain kinds of data (like multiplayer updates).

Post reply on HN