I consider myself a refugee from the old JEE architectures. Threading was handled (naively, for the most part) by the container. Requests were synchronous, transactions distributed. The applications were deployed to a private data center, so scaling the ponderous beast was handled by scaling out (nodes to a weblogic cluster) and scaling up (increasing memory …
The easiest way to get up and running quickly with XOOM, along with an explanation of our position on open source innovation. We’ve decided to introduce a familiar way to learn the different components of the XOOM toolset—without the need to understand everything about our platform up front. It is our belief that all application …
I have been using various forms of messaging for more than 30 years. Messaging has become second nature to me, but I empathize when others say that messaging is to them unfamiliar and intimidating. Since the Actor Model is based on message passing, it stands to reason that this programming model is likewise unfamiliar and …
If you are interested in software designs that feature concurrency, I think you will enjoy this post comparing multi-threading with component development using the Actor Model and actors. Employing the Actor Model means that your components are built using actors. Actors are objects, but ones that send and receive messages asynchronously, and that support concurrent …
With the continuous news about the XOOM/PLATFORM you’ve probably been wondering how you can put the reactive goodness to use. Here I explain how the use XOOM/ACTORS to achieve asynchronous messaging between objects, which are implemented as actors.
Several have requested a document describing the XOOM/PLATFORM architecture. So here it is. This specific article is kept relatively brief. This is in part to emphasize the simplicity of the XOOM/PLATFORM. It’s just not complicated or difficult to describe. The other motivation for brevity is not knowing entirely what architects and developers are looking for in …
This new platform represents my vision for software development from years ago. I have taken a few side tracks along the way. Previously I felt that I would be better off trying to contribute my vision to heavily funded efforts that have multiple teams, those that would easily out perform me alone. That was a …
After a discussion of all those fancy doodahdah filters, routers, and buses, we are back to the plain old Message Channel. Yes, I did skip the Process Manager. We will get back to it, but for now it seems we all need a bit of boredom. Well, not really.
You have a number of disparate business systems, from purchased commodity applications, to custom developed applications that help achieve competitive advantage, to those of integrating business partners. You need all of these systems to work together, although they run on different platforms and have various service interfaces, and each set of service interfaces specifies a …
