The Apache Open For Business Project is an open source, enterprise automation software. The goal of my project is, instead of reinventing the wheel and trying to integrate OFBiz with each system separately, I want to integrate it with Camel and let Camel do what it does best
When my father built his current house a few years ago, he had the pleasure of having to deal with the entire process of building a new custom house based on a simple list of requirements. Once he and my mother defined their list of requirements they started to look at floor plans.
Handling lots of real-time streams of information, when Twitter alone is producing 250+ million tweets a day and 27 million links to news and media, can be a daunting task.
The following sample which demonstrates a nested iterator in the WSO2 ESB. From the second iterate mediator, messages retrieved from the first iterator are again iterated into smaller messages.
Learn the challenges, pitfalls, shortcuts, tips and tricks for building RESTful web services using Node.js. this tutorial will deal with authentication, declarative ways to describe your data structures, and validation.
Decoupling can be achieved and yield flexibility, but this does not mean it is appropriate for every call from one object to another. The best thing to do is start with straight method calls, but keep cohesion in mind.
I don’t know what it is, but it took me a long time to finally wrap my head around the Factory Method. My number one source of information wikipedia featured a very simple example that didn’t seem to drive home the point. Here it is for reference.
As the technology discussion pivots to focus on APIs, teams are wondering how API and SOA converge. Are services simply being re-branded? Are APIs only good for mobile or external use cases? If we publish APIs, do we need SOA? Many architects believe that APIs do not apply to their projects or business use cases.
The presentation, called "SOAP: Service-Oriented Architecture and Programming", Don Box waxes poetic on the objective and subjective conjoining of software components and services.
With recent contributions to Camel, now camel-jcr component has a consumer which allows monitoring a Java Content Repository for changes. If your jcr supports OPTION_OBSERVATION_SUPPORTED then the consumer will register an EventListener and get notified for all kind of events.
Of course the first thing most people would tell you is to look for existing solutions. But even then, there are those times when you need to write your own. Here are just of my reflections on it.
One of the first integration problems that companies encounter when using a new application is data loading. Whether it’s a migrating data from an old product to a new one, managing and cleaning data, warehousing data, or replicating it from one place to another, it’s a painful task.
Are your teams taking advantage of integration points? Or is each integration point implementing identical or similar functionality in an inconsistent fashion?
It was interesting hearing how other developers are using APIs in their projects, and what problems they are encountering and solving. I’ve posted my slide deck for those who are interested. I also recorded audio from the talk and will be posting a link here when that’s online.
James Strachan founded the Apache Camel project with this first commit 6 years ago
Even in the first commit, today's users of the latest Apache Camel releases can see the structure of the route builder, and the API with the component, endpoint, exchange, producer, consumer, et al.
Recently I prepared a demo and thought it might be useful if I share it in my blog. If you are new to WSO2 ESB, it is recommended to refer the following prior posts.
This post is an aggregation of ongoing thoughts I'm having around my role in the API space, a diagram I drew the other day while enjoying an IPA, and inescapable thoughts fueled up by a post by Patrick Meir over at iRevolution, called Crisis Mapping, Neogeography and the Delusion of Democratization.
This post demonstrates using Groovy to explore the standard JMX MBeans provided by the Java Platform as well as the AMX beans that GlassFish provides. The last Groovy code snippet invokes GlassFish's "bootAMX" operation to unleash significantly more GlassFish JMX-based monitoring and managing capabilities.
Long a candidate for improvement, Mule Documentation has recently undergone several foundation-layer improvements that will help us move more quickly as we produce new content and clean up the old.
I've written about this before, but here's a recap and an extra trick which might be useful...
See this demo of ZeroMQ with Microsoft .NET C# using the pipeline communication pattern and find out how I plan to build my HFT platform using ZeroMQ.
In this session you'll see how ZeroMQ - a flexible, lightweight message broker - and gevent - a coroutine-based networking library - are used to create a concurrent and distributed system.
The pattern chains the receiving objects together, and then passes any request messages from object to object until it reaches an object capable of handling the message. The number and type of handler objects isn’t known a priori, they can be configured dynamically.