Hacker News new | comments | show | ask | jobs | submit login

I must say I don't completely understand his point. What comes in the place of messaging middleware such as RabbitMQ?

Even web "2.0" applications still need to send each other messages, both synchronously and asynchronously. For example, to trigger backend work that should not be handled on the web server, and receive the results. Or to notify when changes in data happened.

Incredibly generalized notion based on questionable assumptions. The OP seems to have identified that distributed state is hard. Not news and not in anyway unique to MOMs.

I guess the middleware does less and less. You still need notifications, but most of the data can be taken directly from the database.

I guess it depends on the specific architecture, if you use something like Mongrel2 messaging is used for everything, even for routing HTTP requests and responses to the processes/servers that handle it.

Also, hasn't it always been the case that a lot of web applications communicate with the database directly to fetch information? What's so "web 2.0" about that?

The major thing that changed with AJAX/Comet and Websockets and such is that the javascript running on the end user's browser can now be regarded as an endpoint for message-passing. This increases the amount of messaging, doesn't it? In so far that relying on just polling a database is no longer good practice in our "realtime notificiation" world...

Yeah, maybe Web 1.0 killed the middleware star and Web 2.0 is bringing it back.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact