Unconventional to bundle web socket server with REST API? -


for enterprise rest api (php in case), bad practice include web socket server along rest api? pairing of 2 makes nice mix event dispatching services, i'm not sure if these 2 services different enough warrant separation? guess con can see @ moment, if rest api go down, web socket servers down, removes possibility of having fail-over connected clients, or degree.

if you're looking robust way manage web sockets, check out http://faye.jcoglan.com/ - has libraries javascript, ruby, etc, , runs independently of other servers.

if don't need kind of resilience, wouldn't worry mixing rest , web socket apis on same server.


Comments

Popular posts from this blog

android - Gradle sync Error:Configuration with name 'default' not found -

java - Andrioid studio start fail: Fatal error initializing 'null' -

html - jQuery UI Sortable - Remove placeholder after item is dropped -