It seems that HTTP calls have become a default way to think about distributed systems. HTTP and Web services definitely have a lot to offer, but they are not the only way to do things and there are definitely cases where web is not the right choice. Unfortunately, lots of people just stick with web services and hack on, trying to fit a square peg in a round hole. In cases such as these, a different distribution paradigm can save us quite a lot of time and effort both in development and later in maintenance. One of those different paradigms is messaging.
Tweet
SaveShareSend
Tags: frameworks, opinion, server, web services
-
Why to Use Concurrent HashMap instead of hashtable & synchronizedMap?
-
Primus v1.4.1: rule a project deployment by human readable scenario
-
InfoQ: Google and Microsoft Want to Improve HTTP
-
Protecting a Laptop from Simple and Sophisticated Attacks
-
A gentle introduction to Backbone with jQuery
-
Dynamic View Object in ADF
Add your comment
