JavaOne 2016 Trends: Besides focus on Java platform updates (Java 9, Java EE 8, etc.), I saw three hot topics, which are highly related to each other: Microservices, Docker and Cloud. I also talked about this topic from a middleware perspective. See my slides and lessons learned.
This article shows the different components available for a Hybrid Integration Architecture. The goal is not to discuss different vendor offerings but to explain different concepts and benefits of each component in general and how they relate to each other. Including concepts such as Hybrid Integration Platform (HIP), Cloud-Native Middleware, PaaS, Docker, iPaaS, iSaaS, API Management, and others.
This article discusses how relevant microservices, containers and a cloud-native architecture is for middleware. It is unbelievable how fast enterprises of all sizes are moving forward with these topics!
Apache Camel is my favorite integration framework on the Java platform due to great DSLs, a huge community, and so many different components. Camel is used by many developers from different companies all over the world. However, most guys are not aware that some really cool tooling is available for Camel, too. Many people ask me about Camel tooling when I do talks at conferences. This is the reason for this short blog post about Camel tooling.
This week, I was at Confess 2012 (http://2012.con-fess.com) in Leogang, Salzburg (Austria). Confess is an international conference for Java professionals in its fifth year, organized by IRIAN and the EJUG Austria. It is reasonably priced with 275 € for the two-day conference, and 500 € for the workshop day. The speaker lineup is very good with many well-known international speakers, such as JSF spec lead Edwuard Burns from Oracle America, Hazem Saleh from IBM Egypt, or Jürgen Höller from SpringSource.
Data exchanges between companies increase a lot. The number of applications, which must be integrated increases, too. The interfaces use different technologies, protocols and data formats. Nevertheless, the integration of these applications shall be modeled in a standardized way, realized efficiently and supported by automatic tests. Such a standard exists with the Enterprise Integration Patterns (EIP) , which have become the industry standard for describing, documenting and implementing integration problems. Apache Camel  implements the EIPs and offers a standardized, internal domain-specific language (DSL)  to integrate applications. This article gives an introduction to Apache Camel including several code examples.
Three lightweight integration frameworks are available in the JVM environment: Spring Integration, Mule ESB and Apache Camel. They implement the well-known Enteprise Integration Patterns (EIP, http://www.eaipatterns.com) and therefore offer a standardized, domain-specific language to integrate applications.
These integration frameworks can be used in almost every integration project within the JVM environment – no matter which technologies, transport protocols or data formats are used. All integration projects can be realized in a consistent way without redundant boilerplate code.
This article compares all three alternatives and discusses their pros and cons.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.