From the webpage:
Most people who ever worked in real-world data integration projects agree that at some point custom code becomes necessary. Pre-fabricated connectors, filter and pipeline logic can only go so far. And to top it off, using those pre-fabricated integration logic components often becomes cumbersome for anything but the most trivial data integration and processing tasks.
With RESTx – a platform for the rapid creation of RESTful web services – we recognize that custom code will always remain part of serious data integration tasks. As developers, we already know about a concise, standardized and very well defined way to express what we want: The programming languages we use every day! Why should we have to deal with complex, unfamiliar configuration files or UI tools that still restrict us in what we can do, if it is often so much more concise and simple to just write down in code what you want to have done?
Therefore, RESTx embraces custom code: Writing it and expressing your data integration logic with it is made as simple as possible.
Let me illustrate how straight forward it is to integrate data resources using just a few lines of clear, easy to read code.
In my experience “custom code” means “undocumented code.” But leaving that mis-giving to one side.
RESTx gets us part way to the TMDM by its use of URIs.
We just have to use them as appropriate to create TMDM output for further integration with existing resources. That is we have to decide which of these URIs are subjectIdentifiers and which function as subjectLocators as part of our integration activity.
I have just started to wander around the Mule site. Feel free to suggest examples or places I need to look at sooner than others. Examples of RESTx output as topic maps would be nice! Hint, hint.
PS: I’m got a small data set I need to clean up for a post next week but I am also planning a post on URIs, simple or complex identification?