This session will introduce the challenges with current SOA and integration platforms, then elaborate on how these challenges are addressed via the key themes of ease of use, agility and flexibility.
It will also illustrate that whilst many developers may not think of what they're doing as integration - for example leveraging and mashing up RSS feeds, web services, data bases, sending instant messages - the capabilities of light weight, pragmatic SOA and integration platform can simplify these tasks.
The pluggable and loosely coupled approach also enables inherent scalability without explicit coding. By eliminating unnecessary bolier plate code and giving the developer the choice of what languages and technologies to use they can focus on being productive in solving their business problems rather than fighting artificial restrictions of the framework.
Another key goal is that of small footprint and modularity, to "size to fit" the runtime. This means the runtime environment should only include the capabilities needed by the application. To achieve this Fuji uses OSGi, a module framework for Java. The framework and every component, interceptor and application is an OSGi bundle to make the platform completely modular. This also allows Fuji to run directly in any OSGi 4.1 compliant container. It can also run in the GlassFish v3 application server which has native OSGi support, so it can leverage the great scripting support and other features of this application server.
The demo will show the two ways to approach Fuji for a developer - or even a casual technologist:
1. A web based visual tool allows the dragging and dropping of external adapters as well as services to inspect, filter and transform the messages.
2. A domain specific language called "Integration Flow Language" (IFL) to express the routing of messages between services, combined with Maven based templates and tooling to easily define and run applications. This gives the user the freedom to use any IDE with Maven support.
The technology demonstration will also show how quick and easy an integration application can be developed iteratively. The demo is primarily built via configuration by filling in templates; very little actual coding needs to be done