What are the main reasons to migrate to Websync 4?

[blackadder]

I have been running 3.5.0.2 for some time and things appear to be running fine. What are the main advantages to migrating to version 4? Are there performance gains? I do not think there are any new features that I would need right now. However, we pump megs of data per second so any performance increase would be helpful.

[Anton Venema]

In general, I would say "if it ain't broke, don't fix it". WebSync 3 is extremely fast, stable and capable, so if you don't need the new features and you aren't seeing strain on your clients or servers, I would probably leave it alone.

That said, there are definitely some performance-related improvements in WebSync 4. Have a look and see if these are useful to your application.

- The core engine has been improved.

WebSync 3 has been tested up to 100,000 peak message deliveries per second. WebSync 4 is currently testing up to 300,000. There are also various stability improvements that were only possible to implement in a new major version.

- Binary network serialization can reduce network bandwidth consumption.

WebSync 4 sends binary payloads over the wire as actual binary. In WebSync 3, you had to base64-encode binary payloads, which results in about a 33% increase in payload size.

- WebSockets reduce HTTP overhead.

WebSync 4 supports native WebSockets as a transport protocol, which eliminates a lot of HTTP processing overhead, most noticeable on streaming connections with frequent publications.

Also, as you would expect, all new feature development is going into WebSync 4. WebSync 3 will continue to be maintained with bug fixes, but new features and platform support will target version 4.

Anton Venema

Frozen Mountain Software
604-227-2458 (Canada)
919-300-5520 (United States)
888-379-6686 (Extension 102)
www.frozenmountain.com

On Tue, Feb 19, 2013 at 2:09 PM, blackadder <mdblac...@gmail.com> wrote:

I have been running 3.5.0.2 for some time and things appear to be running fine. What are the main advantages to migrating to version 4? Are there performance gains? I do not think there are any new features that I would need right now. However, we pump megs of data per second so any performance increase would be helpful.

--
You received this message because you are subscribed to the Google Groups "WebSync" group.
To unsubscribe from this group and stop receiving emails from it, send an email to websync+u...@googlegroups.com.
To post to this group, send email to web...@googlegroups.com.
Visit this group at http://groups.google.com/group/websync?hl=en.
To view this discussion on the web visit https://groups.google.com/d/msg/websync/-/Q0pnwxs9P5MJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[blackadder]

Thanks Anton.

It has been a while since I implemented this so this may be a dumb question. I am using the .Net client directly and using json. Is it possible to use binary serialization in this case? Is that something I would need to upgrade to version 4 to get? I do not remember any configuration for the serialization method used.

[Anton Venema]

WebSync 3 *always* sends data over the network as JSON. Even if you have a binary-formatted data payload, you still have to send it over the network as JSON, which means first encoding it to a base64 string.

var dataJson = JSON.Serialize(Convert.ToBase64String(binaryData));

RequestHandler.Publish("/channel", dataJson);

WebSync 4, on the other hand, can send data over the network as JSON or as raw binary. There are overloads on all the publish methods that take a byte array. This byte array is sent over the network as raw binary without the overhead of base64-encoding.

WebSyncServer.Publish("/channel", binaryData);

Does that answer your questions?

Anton Venema

Frozen Mountain Software
604-227-2458 (Canada)
919-300-5520 (United States)
888-379-6686 (Extension 102)
www.frozenmountain.com

To view this discussion on the web visit https://groups.google.com/d/msg/websync/-/lyQu2IDk_yUJ.