Is Warewolf a Service Bus?

For a long time we have really battled to put Warewolf into a neat box. It is a powerful, unique and multi-faceted system that we’ve never been able to categorise. It’s been a massive frustration as a marketer when I’ve tried to communicate this “thing”.


The idea behind Warewolf started as a frustration with how the current software development environment is. It can be overly complex where the developer is unable to see the wood for the trees, buried in lines of code. Business and IT cannot see eye to eye because they don’t speak the same language, a massive impediment to both parties who should be working together. Developers are frustrated with building the same capture form over and over where their skills could be better utilised without all the noise.

The idea is to remove the unnecessary and mundane from software development in a way that business and IT can work together to take the company forward in a meaningful way. Make common things easy to reuse with pre-built components. Empower developers by freeing them up to work on the cool stuff and the big picture.


So with all this in mind the journey began to build a system that could deliver on this. In our early days we were convinced that we could provide “SOA in seconds” with this application. In fact, when we were very much in our alpha (pre-beta) stage, we started a campaign to find a closed group of alpha users to test, feedback and ultimately become our core of first-ever users. While we did manage to get over 150 subscribers, there are very few who still actively use the application today, and very few gave us feedback. They were not seeing what we were seeing. Ouch.


We then took a strategy of testing a multitude of different landing pages to see which one converted the most visitors into hard-core users. We had, and still do have, pages that highlight Warewolf as a fast application development tool, an easy integration tool, an API management tool, a BPM platform, something with awesome re-usable components, a Microservices Architecture platform, a Rapid Prototyping platform and even something that visually represents business logic.


We tweaked, we optimised, we ran focus groups, but somehow there was still something missing. While Warewolf does do all of these things, and very well, there was nothing tying it all together. The idea was not easy to explain to anyone in a single sentence. Enter Service Bus. Here was a concept that finally allowed the penny to drop. With one simple term all of Warewolf was described, and neatly defined into a comfy, left-brain category. Hooray!


As a Service Bus Warewolf is unique in the features it has and how it works. It is lightweight yet still gives you the power to easily integrate into other systems. It offers secure messaging and is easy to maintain with its visual IDE. It is uncomplicated, making it easy to learn and simple to use. Because it’s visual, and uses concepts of flow-based programming, it’s code language agnostic – making it usable and accessible to any developer.


As exciting as it is, we are reminded how far we still need to go. Big, key features still need to be developed before the application is truly scalable and highly performant. There is still a lot to do on the user experience side to make it more intuitive and obvious to use. At least, though, we know that all of the awesome features  we are developing hang so well off this Service Bus we call Warewolf. Secure, easy and coding language agnostic.






  1. Rider

    Hi There

    You mention that this is a service bus. We are interested in using one but your buss does not mention any EIP components? Do you support them?


      1. Hi Rider

        In response to your private message –

        At present we have focused on creating a service bus that is easy to use, setup and implement. In doing so we have yet to develop some of the other features such as messaging, event sourcing etc. However, as I mentioned these are definitely items that need to be implemented. Unfortunately at this point we cannot say when we will be delivering them.

        Every Warewolf service is exposed as a webservice that can always be used as an integration point. Warewolf is also able to integrate with databases in the form of Stored Procedures, DLLs and web services. However we have not yet tested or attempted direct integration with JPA, EJB or JAX-WS.

        Is it possible for you to provide us with examples or what you guys look for when evaluating an ESB? It would prove very helpful to us and we can prioritize making them available.

        Feel free to do this in the Community or mail me directly: wallis at warewolf dot io



    1. At present Warewolf Easy Service Bus allows for orchestration and multiple ways of performing composition. However components like messages queues, event sourcing or routing and Pub/Sub event model has yet to be developed. Being open source there is obviously an opportunity for these to be implemented via the community ;).

      They are on our list and we will get to them dependent on feedback we get from users.

      Thanks for your interest and we would appreciate any information you can share on the use case you trying to implement :).

  2. Pingback: How does Warewolf integrate into software architecture?

Leave A Comment?