Hello again everyone, today Cody and I will be shifting gears a bit and heading toward a different part of the Red Hat Portfolio, Red Hat JBOSS EAP. Red Hat JBOSS EAP is actually an older part of the Red Hat portfolio and has been a product subscription we’ve offered since 2006. That makes it older than all the other products we’ve spoken about up until now except for RHEL (Red Hat Enterprise Linux). Red Hat JBOSS EAP is also unique because it is part of Red Hat’s Application Development Products which we haven’t really touched on yet except for the aspects of Red Hat OpenShift that are developer focused. We hope you enjoy this week and the coming weeks as we dive into the more application development side of things.
I’ve said it before but I’ll say it again, all of the Red Hat products come from open source technologies and Red Hat JBOSS EAP is no different. The upstream project that the Red Hat JBOSS EAP comes from is Wildfly. At its core Red Hat JBOSS EAP is an open source platform for Java applications. It can be used for the creation, management, and deployment parts of your application lifecycle to allow you to create and deploy your applications at scale across multiple types of environments in the enterprise.
Some of the features Red Hat JBOSS includes are: distributed caching for scaling up demand for applications, transaction manager to help build transactions into your apps that are based on the ACID model, and high availability clustering for reliable and fault tolerant delivery of application services to your customers.
Red Hat JBOSS EAP has also begun to enable the Hybrid Cloud deployment of Java applications by running seamlessly in AWS Azure and of course, Red Hat OpenShift. This makes it ideal for organizations who are transitioning to a Hybrid Cloud environment but still want to reliably run the legacy applications they’ve come to rely on and trust. There are so many things about Red Hat JBOSS EAP that make the developer’s life easier and helps make their applications run the way they intend. Now I’m no developer but Cody knows a thing or two about that life and I’ll hand it over to him to talk about what he thinks is interesting about Red Hat JBOSS EAP.
Thanks Cam for that great introduction on JBoss EAP. As I am sure everyone who is familiar with JBoss will attest that it is a great application, but for those that aren’t aware JBoss EAP stands for JBoss Enterprise Application Platform. This really helps sell what JBoss is better than Cam or I ever could. JBoss at its core is a set of libraries and dependencies that you can use to develop and run enterprise applications on.
As Cam mentioned I was a developer in a past life. In this past life I did come across JBoss EAP. At the time I didn’t realize that it was part of the greater Red Hat ecosystem. Red Hat wasn’t a common name to me which has since changed. For those of you who have read my personal posts you know I worked for a company called Rockwell Automation. This company made Manufacturing Applications. At the time their newest release was a modular solution that could be used to provide insight into manufacturing operations. It was a web based application which would be spun up on an internal server system and accessed internally.
JBoss was the perfect platform for this as it allowed us to deploy each application piece by piece as well as provide updates in packages to the applications without taking them offline. This is especially important in a manufacturing plant where scheduled downtime sometimes only occurs every 2-3 years. Unscheduled downtime can obviously lead to a decrease in overall plant efficiency. This is quite the conundrum when you account for the fact that application updates can often include important security, usage, and other product updates. Balancing these requirements means you need an application platform like JBoss.
Like many enterprise applications JBoss is designed to run extended periods of time without going offline and provides stability when it is truly needed. These are the types of reasons organizations turn to companies like Red Hat as opposed to developing their own homegrown solutions. Providing support, training and stability is what Red Hat advertises and it's why Cameron and I decided to write these blog posts. We wanted to show how their applications can make a difference and this is the first product we have written about where we have first hand experience of the difference that's been made.
Next week we will continue our discussion on JBoss and Red Hat Application Services. We hope you enjoyed this post. Please feel free to reach out with anything we should change or any discussion tips and as always go to Red Hat’s website to find out more on any of these products. Thanks!