SOA (Service Oriented Architecture) is an acronym that has been gaining in popularity over the past few years:

Flux jobs are executed in a job tree. The job tree is similar to the concept of a file system where jobs (like files) are stored in namespaces (or folders). Each job has a namespace where it executes. All jobs execute underneath the root namespace and can execute in sub-namespaces.

It's neat to see users push the envelope of our software. Flux evaluators often test performance and scalability of Flux to determine if it will satisfy their needs. We've watched the needs of users evolve and have changed the functionality of Flux to meet their needs.

We've been getting a lot of great feature requests from customers ever since we initially announced the Flux Web-based Designer. These requests have driven development and really improved the Web-based Designer. One of the most common requests that we have received is to support embedding the Web-based Designer, which was added in Flux 7.5. We're building on this feature in the upcoming 7.6 release due out 12 November 2007. Flux 7.6 will support monitoring flow charts in the embeddable Web-based Designer. This will allow you to easily support rich workflow operations for your Java web applications. Embedding the real-time monitor will allow your users to easily export, view, monitor, and change running flow charts without leaving the comfort of your web application.

We hear you loud and clear and have added a few new examples to illustrate custom actions and how they integrate with the Web-based Designer. The new examples can be found in our Customer Portal at:

We have an opening for a Web Designer and are in search of the right person for the job.

I’ve had the pleasure of doing some performance testing against our supported databases lately. It’s really interesting to see concrete performance metrics to compare the impact that the database has on the performance of Flux.