Spring Integration is an EAI framework offering simplified ways to solve EAI tasks such as message transformation and routing. Architect Mark Fisher wrote about the project & Rod described it in the video) as an implementation of several EAI patterns from Grgor Hophe's book. The project is currently in 0.5 but 1.0 final will be released in Q2 & support:
Another message routing & transformation framework that integrates well with Spring is Mule ESB, which was present at last year's The Spring Experience.multiple configuration formats (XML, namespace, and annotations), point-to-point and publish/subscribe channels, and several adapters (minimally: JMS, RMI, HttpInvoker, Hessian/Burlap, File, EMail, JDBC, stream, and Spring ApplicationEvents). It will also work seamlessly with Spring's transaction management and dynamic language support.
SpringSource will be building a number of value-ad tools on top of it's free and open source programming models & frameworks. The initial product set include the SpringSource's Application Management Suite, Tools Suite, and Adanced Pack for Oracle Database.
The Application Management Suite, built jointly with Hyperic, and will offer:
- Auto-discovery of Spring-managed applications and components and the platforms and application servers that they run on
- Monitoring of Spring applications, components and runtime
- Custom alert configuration and corrective actions
- Performance and service-level report generation
- Automatic calculation and updating of baselines for metrics
- JConsole support
The Spring Tools Suite was covered by InfoQ before and builds on the Spring IDE & Eclipse Mylyn in order to ease the development of large Spring applications, and incorporate other key features, ranging from issue tracking to code quality, in order to better support a Spring application’s entire lifecycle.
Starting Jan 15th certification on the Spring framework will be available, with certifications on "Web Technologies”, “AOP Methodologies”, and "Enterprise Application and Information Integration” coming later in the year.
On Thursday evening, Forrester analyst John Rymer keynoted on application platform trends, in which he mentioned that while in the past we had commercial vendors & committees of vendors innovating in both runtimes & programming models - open source projects such as Struts & Spring were successful examples of programming models that emerged driven by open source. Going forward, John predicted open source will take on the role of providing the programming model, while commercial vendors provide the runtimes those programming models run on or are improved by.
This trend was echoed by Rod in the video interview above when asked about how they will maintain their open source culture now that they also have pure-commercial offerings. Rod pointed out that Spring itself and the Spring portfolio is Apache licensed and will remain so; in addition, new programming models such as Spring Integration will also be done as open source:
SpringSource's business strategy going forward however will be to provide value-added runtimes for commercial subscription customers to complement their open source programming models. Rod emphasized that their new business model will allow them to grow in a way that will enable them to contribute even more to open source.We really think that open source is the only way to define programming models today, we are not in the business of creating proprietary programming models.
Community comments
Spring Messaging Roadmap - MDPs to EIS Patterns
by Srini Penchikala,
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Baron Davis,
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Rod Johnson,
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Steven Devijver,
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Rod Johnson,
Spring Messaging Roadmap - MDPs to EIS Patterns
by Srini Penchikala,
Your message is awaiting moderation. Thank you for participating in the discussion.
This is very interesting development in the Spring Portfolio components. With support for Message Driven POJOs (MDP) introduced in v2.x, it was only matter of time for Spring folks to support the popular EIS patterns that Gregor and Bobby documented in their book.
Is the video uploaded yet? I don't see on the web page.
-Srini
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Baron Davis,
Your message is awaiting moderation. Thank you for participating in the discussion.
@JXInsight
Why should we care? You are commercial vendor anyways.
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Rod Johnson,
Your message is awaiting moderation. Thank you for participating in the discussion.
William
This was a high level announcement. We are doing a huge amount of work in instrumenting Spring internals, as well as the specific Hyperic integration. The data produced from that instrumentation will likely be exposed as an SPI. You are welcome to approach us to discuss that--I think at present you are jumping to conclusions.
Note: SpringSource is a company that overwhelmingly produces and maintains Apache License open source software--millions of lines of it. So saying that JXInsight is a "commercial vendor just like SpringSource" is a bit misleading. (Not that I am criticizing you for being a commercial vendor.) You make a valid point regarding access to SpringSource management features being largely (not entirely) applicable to production. However, our management suite is just one part of a broad range of benefits across our subscription products that span development through production.
This was a high level announcement. There likely will be an SPI. The deep instrumentation of Spring internals we're doing will enable us to expose one.
Rgds
Rod
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Steven Devijver,
Your message is awaiting moderation. Thank you for participating in the discussion.
Having profiled a big Spring application with Quest's Performasure I don't see what the fuss is about. Actually, we tried to get performance statistics with AspectJ as well and found that this approach worked very well too.
So, even if SpringSource doesn't provide an SPI - and if such a thing would be useful for Spring users - I don't see how hard it can be to provide this as an alternative to what SpringSource would be offering.
Re: Spring Messaging Roadmap - MDPs to EIS Patterns
by Rod Johnson,
Your message is awaiting moderation. Thank you for participating in the discussion.
William
Frankly I think you are coming across as negative and defensive. That's a pity, as I've already indicated that we are open to working with you (and other vendors) in future, and we've made no negative comments on your products or company. We believe that the SpringSource team has a unique understanding of the Spring runtime and that it's a logical extension of our desire to provide the best solution to our customers to gather and expose management information. That does not "exclude" other solutions (which can surely compete on merit), and does not preclude our information being exposed via an SPI, as I've already mentioned. We certainly envisage that Hyperic will not be the only other product used in conjunction with our offering.
Rgds
Rod