Asyncronous Middleware Systems

The communication between different computers have grown more difficult with the introduction of different Web services and more flexibility needed between different computer systems. While many processes were running internal in the computer before, the communication between processes was secure, safe and quick. I don’t say that there were not problems before, but just that the problems were in a smaller scale than today. With the Internet and a lot of the technology presented through it new problems arise. Could a service run on one computer while waiting for an answer on another computer. How could a system keep on working if a component is not responding? How can systems built up on different foundation work together? That are some of the question “Asynchronous Middleware Systems” are supposed to give an answer to.

This course I took and I found it interesting during the lectures. Some of the ideas made by the computer companies makes the world a lot easier for us trying to work with the complex API and and world that is starting to be more integrated while its more complex to understand.

The principles behind the Middleware Systems are to give the programmers a higher level of abstraction. To use the function implemented in many of these systems the programmer don’t need to focus on all the details to make communication possible. Services provided from these systems are e.g. Invocation, transaction, security and naming. And this is made possible with e.g Queing, messaging and publish/subscribe functionality.

I started the main-reading to this exam today and hopefully will I know a lot more about this stuff before the exam.

Leave a Reply

Your email address will not be published. Required fields are marked *