SocketStream apps in the wild

[Paul Jensen]

Hi,

I'd like to compile a list of apps that are using SocketStream, partly out of curiosity, but mainly for a dev resource center for work. If you have an application and you're happy to share a link and/or a description of it, please leave a comment here.

Regards,

Paul Jensen 

[Robert Hall]

Well, there's https://dashku.com/... :P

[Skipster]

Michele's Day - http://michelesday.com. The site is a mash-up of Cozi and Evite, with Match.com tendencies. It's open to new users, but in very early beta. More like alpha.

Uses Ember, Mongo, Redis, and a proprietary DB layer that I call "Ember Documents".

Other technologies we tried, that failed (at the time -- 1 year ago) where Ember+ss-0.3 succeeded: Meteor, Angular, Derby, Batman, Knockout.

After a year of reflection on my tech stack, I feel Ember was the solid choice, and the one that can scale. BUT a word of caution. Handlebars is a real stinker, and will drive you crazy and make you crave the rich data bindings of Batman and Knockout, or Angular's beautiful attribute-based data bindings. Emblem.js is a small concession to make me feel better -- at least I will be able to take that nasty Handlebars grammar out of my Jade templates (ss-clientjade). But the data bindings being so stupidly primitive leads to HEAVY use of handlebars helpers, view properties, and controller properties, and overly brain-dead templates. That is code scattered across 4 architectural tiers, if you have noticed, which I jokingly call MVMVVVVC, as opposed to the industry's MVC and MVVM. A real mess. It is not nice. But certainly trumped by stability. And Ember has definitely smoothed out over the past year.

[Paul Jensen]

Thanks Skipster, especially for sharing your experience on developing it with Ember.

[---VLi---]

Cresco Metrics Flow (Beta) - recruitment assessment service having two SocketStream SPA-clients:

-https://www.cm-flow.com/flow/51a0ec58f1856f0200000008 (candidate UI with example assessment) 

-https://www.cm-flow.com/control#!/home/signin (customer & assessment-designer UIs)

Using only RPC (no pub-sub yet) and running it in Heroku...so engineio polling.

Other technologies in the stack:  Angular.js, Node.js, MongoDB/Mongoose, CofeeScript, Stylus, Jade, Zurb Foundation… 

Overall it has been pleasure to develop with this stack.

Right now trying to figure out should I be worried about "Connection down :-( "s happening for ~5% of users in my light stress test setup ( ~40 concurrent users by Iron.io-workers+phantom calling sequence of SS RPCs, like real users will do).

Br, ---VLi---

[Alex Birkett]

Hi Paul,

I met Owen when he came to give a talk in Oslo last year. He convinced me to give SocketStream a try. I've just released the Location IO demo based on SocketStream, Google Maps and Angular JS. https://npmjs.org/package/demo.location.io (Live version here: http://demo.location.io)

I'm looking into a business cases for this technology. I'll need to recruit people to help me. If this scratches anybody's itch, let me know.

Regards,

Alex Birkett

[Dariusz PAWLAK]

Our social SPA site is: http://rnc.rodzicenaczasie.pl
It is dedicated for parents which have kids in pre- and schools.
Current stage is: private beta testing. Some piece of functionality dosn't work properly and stable.

This is our first nodejs application. Still learning server JS technology, which is very impressive.
We are using a lot of RPC functions.

Main used technologies are: 
* server: SocketStream, Node.js, MongoDB/Mongoose, Redis, Authom,
* client: Angular.js, jQuery

I hope SS is growing his community and popularity.

[Robert Hall]

We pushed a site live yesterday that hit the front page of the NY Times! (Crazy!)

http://hollowdocumentary.com/

I can see some of you asking why we needed sockets. In reality, we didn't. When we first set out, we thought we would end up doing realtime things in some of our data visualizations, but that never quite panned out. Still, in our next round we'll probably be adding sockety stuff so it's a good foundation. We do use the RPC stuff for one or two data visualization APIs, but that could have been simple AJAX.

JUST THE SAME this site has been humming along mercifully well. So mad props to Owen. I think you can stop saying 3 is not "production ready" and just tell people to start contributing in the name of making SocketStream 4 to have a "more" production ready site.

Props to *everyone* who has helped me out along the way. First for SS! Front page of NY Times!

-- Robert

On Monday, May 20, 2013 5:14:32 PM UTC-4, Paul Jensen wrote:

[Robert Hall]

Oh, one more thing.

This is anecdotal, but SS really is built well. I have thoroughly enjoyed how compartmentalized things are. It's made build processes so smooth and easy, which is fantastic for redeploys.

[Davis Ford]

Robert -- that's a really impressive / touching docu-webmentary !!   Nicely done.  I really enjoyed scrolling through it.

--
You received this message because you are subscribed to the Google Groups "SocketStream" group.
To unsubscribe from this group and stop receiving emails from it, send an email to socketstream...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

http://daisyworks.com

@zenocon

[Dariusz PAWLAK]

I got an error:

WebSocket connection to 'ws://hollowdocumentary.com/engine.io/default/?uid=26692950353035113342087716&transport=websocket&sid=QAdYB-kNWCnBtrYqAC6X' failed: Unexpected response code: 200 http://hollowdocumentary.com/
WebSocket connection to 'ws://hollowdocumentary.com/engine.io/default/?uid=26692950353035113342087716&transport=websocket&sid=QAdYB-kNWCnBtrYqAC6X' failed: WebSocket is closed before the connection is established. http://russgold.cachefly.net/assets/app/1371856429786.js

And page dosn't load.

[Robert Hall]

Thanks Davis!

[Robert Hall]

Appreciate the feedback. Would you mind sending me stats in CVS form? http://supportdetails.com/

This is our general technique for squashing bugs.