Jakarta EE is officially out

Jakarta EE is officially out! OK, given the amount of publicity and evangelising we and others have done around EE4J and Jakarta EE over the past few months, you would be forgiven for thinking it was already the case, but it wasn’t … until today!

I cannot stress enough how important this is to our industry. The number of Java™ developers globally is estimated at over 14 million. The Java EE market is estimated at a high multi-billion dollar value to the industry. Yes, there are other languages out there and other frameworks but none of them have yet made the impact Java™ and Java EE has over the years. Of course, Java EE was not perfect for a variety of reasons, but if you consider how much of an impact it has had on the industry given known and debated limitations, just imagine how much it can bring in the years ahead if it were improved.

With the release of Jakarta EE, we all have a chance to collaborate and build on the good things it inherits, whilst at the same time working to evolve those pieces which are no longer relevant or perhaps never were quite what was needed. Working within the open processes of the Eclipse Foundation vendors, Java™ communities, individuals etc. are all able to interact as peers with no one vendor holding a higher role than another. We’ve seen this exact same process work extremely well in a relatively short period of time with Eclipse MicroProfile and I believe Jakarta EE can do at least as well.

When talking about Java EE and now Jakarta EE some often focus only on the technologies. Fortunately, those of us who have been in the open source world long enough appreciate that the community is just as important. With Jakarta EE, all of us involved in working towards the release hope that we can use it as a catalyst to bring together often disparate Java™ communities under a single banner. Too often, Java EE has been a divisive topic for some vendors and some communities, resulting in fractures and often working on the same problems but pulling in different directions. If Jakarta EE does only one thing, and that is bringing everyone together to collaborate, then I would still deem it a success!

I’ll finish by discussing why Red Hat® has been helping to lead this effort along with others. I can summarise this pretty easily: enterprise Java™ remains critical to our customers and communities, and we believe that despite the increase of other languages and frameworks, it should remain so for many years to come. Red Hat, and JBoss® before it, has contributed to J2EE™, Java EE, and Eclipse MicroProfile for years, and we believe that sharing our experiences and working on open source implementations is important for the industry as a whole, no matter what language you may be using. We believe it’s important to leverage Jakarta EE in the cloud and to a wider range of communities than in the past. We’re here to stay and will continue to help lead!

Onward!

To learn more, join these upcoming live sessions:

Red Hat makes Node.js a first-class citizen on OpenShift with RHOAR, by Conor O’Neill, nearForm

Red Hat’s offering in cloud-native application development has just taken another step forward with the announcement of supported Node.js. Conor O’Neill from our partner nearForm shares his thoughts on the role that Node.js and Red Hat OpenShift Application Runtimes (RHOAR) will take in Red Hat’s market leadership in Cloud-Native application development, modernization and migration.

Read more here: Red Hat makes Node.js a first-class citizen on OpenShift with RHOAR, by Conor O’Neill, nearForm

Luis I. Cortes. Senior Manager, Middleware Partner Strategy – @licortes_redhat

Learning Process Driven Application Development with JBoss BPM

Are you interested in an introduction to the concepts of process management (BPM)?

Do you want to learn how your business can leverage process driven application delivery?

Are you looking for an easy to understand guide to mastering Red Hat JBoss BPM Suite tooling?

Do you want a step-by-step introduction to setting up JBoss BPM Suite, then coverage of practical and important topics like data modeling, designing business rules and processes,  detailed real world examples, and tips for testing?

For the last few years I’ve been working on putting years of working with JBoss BPM Suite, community projects Drools and jBPM together in one easy to understand book.

In 2017, Red Hat put the first chapter online for free and literally thousands downloaded it starting their journey on the road to delivering process driven application with JBoss BPM Suite. Many of you have reached out over the years to ask about the completion of this book and where you can get it.

The good news isthat the book is available and Red Hat’s providing ebook downloads for free!

Let’s look at how this works, shall we?

Continue reading “Learning Process Driven Application Development with JBoss BPM”

Cloud Native Application Development – Adopt or Fail

In today’s digital world, software strategy is central to business strategy. To stay competitive, organizations need customized software applications to meet their unique needs — from customer engagements to new product and services development. Drawn-out development projects are no longer acceptable, given business demands. Therefore, the need to speed up application development, testing, delivery, and deployment is no longer optional but a must-have competency.   

At the same time that developers are confronting this challenge to deliver solutions more quickly, they are also facing the most diverse technology ecosystem in the history of computing.  To address this challenge, development teams must modernize architecture, infrastructure, and processes to deliver higher-quality applications with greater agility.

Cloud native development is an approach to building and running applications that fully exploits the advantages of the cloud computing model.  Cloud native development multidimensionality involves architecture, infrastructure, and processes based upon four key tenets:

  1. Services-based architecture: could be microservices or any modular loosely coupled model for independent scalability and flexibility of maintenance and polyglot language runtimes.
  2. Containers and Docker image: as the deployment unit and self-contained execution environment with consistency and portability across cloud infrastructures.
  3. DevOps automation: implementing processes and practices and instrumentation of development to test deployment of applications.     
  4. API-based design: The only communication allowed is via service interface calls over the network. No direct linking, no direct reads of another team’s data store, no shared-memory model with an outside- in perspective.

Continue reading “Cloud Native Application Development – Adopt or Fail”

Announcing Red Hat Fuse 7.0 Technical Preview 3

On November 2, 2017, we announced the technical preview of a new low-code integration platform called Red Hat Fuse Online. This technical preview provided a first chance for users to experience the new platform and provide feedback.

Building on the feedback we’ve received with the  Red Hat Fuse Online technical preview, we are happy to announce the Red Hat Fuse 7.0 technical preview 3 (TP3).

Continue reading “Announcing Red Hat Fuse 7.0 Technical Preview 3”

A DevOps approach to decision management

Sometimes we would like to change the behavior of an application fast. I mean, really fast.

Traditional development cycles for enterprise applications take weeks if not months for a new version to be ready in production. Even in the world of DevOps, containers, and microservices, where we can spin up new versions of an app in days, or even hours, we need to go through development cycles that are too far away from the business users.

Welcome to the world of business rules and decision services, along with low code development.

Continue reading “A DevOps approach to decision management”

“Micro-rules,” event-driven apps, and Red Hat Decision Manager

As we described in an earlier blog, microservices are mini-applications which are devoted to a single, specific function. They are discrete (independent of other services in the architecture), polyglot with a common messaging or API interface, and they have well-defined parameters.

As application development and IT operations teams have started streamlining and speeding up their processes with methodologies like Agile and DevOps, they have increasingly begun treating IT applications as microservices. This breaks up potential bottlenecks, reduces dependencies on services used by other teams, and can help make IT infrastructure less rigid and more distributed.

One area where we are seeing this looser, more distributed approach to service development is with business rules.

“Micro-rules”

Business rules and processes in a traditional structure tend to be centralized, with the complete set of functionality defined for all workflows. The problem with centralization is because there is a single, centralized collection of business rules, any changes to one set of rules can affect many other sets, even those for different business functions.

Micro-rules essentially treat each functional set of rules as its own service — well-defined, highly focused, and independent of other rules.

Figure – Function rule sets as micro-rules

Continue reading ““Micro-rules,” event-driven apps, and Red Hat Decision Manager”

Announcing: Red Hat Decision Manager 7.0 Is Now Available

Red Hat has announced the release of Red Hat Decision Manager 7. Decision Manager is the evolution of Red Hat JBoss BRMS and provides a platform to develop rules-based applications and services.

As applications and services become more central to business strategies, business users will become increasingly involved in the development process. Software that aids in creating applications without directly writing code is known as low-code development. Decision Manager provides tools, including an updated UI and enhanced wizards, that help business users participate more actively in application development.

Major Use Cases

Decision service as a microservice

Decision Manager has a more modular architecture, such as a decision service, an execution server, and a management interface. Each component can be containerized and deployed as an image on Red Hat OpenShift Container Platform. Developers can create discrete services for specific needs and deploy those “micro-rules” in a microservices architecture. This approach is covered more in another blog post.

Continue reading “Announcing: Red Hat Decision Manager 7.0 Is Now Available”

The Business Value of JBoss Enterprise Application Platform – latest white paper by IDC

The latest edition of the white paper titled “The Business Value of JBoss Enterprise Application Platform,” which summarizes the benefits and value that Red Hat customers are seeing by moving to JBoss EAP, has been released.

As the paper states, “IDC interviewed organizations that are using JBoss EAP to develop and run various business applications. These study participants explained that they not only have significantly reduced platform costs with JBoss EAP but also are supporting important organizational IT initiatives such as containerization, microservices, and hybrid cloud use.” The interviewed participants varied in size from medium to large organizations and belonged to a set of diverse vertical industries.

Some of the results from this study are:

  • 481% 3-year ROI
  • 8-month payback period
  • $50K USD average annual benefits per 100 users
  • 43% more number of new application released per year
  • 21% faster time to deliver new applications
  • 38% more number of new features released per year
  • 74% less productive hours lost due to unplanned downtime per year

Continue reading “The Business Value of JBoss Enterprise Application Platform – latest white paper by IDC”

Taking Control of your IoT APIs

At its core, IoT is all about data: data from devices, commands to devices, integrating IoT data with other data to gain insights. The data sources include devices, enterprise applications, vendor/partner systems, service providers and customers. The point-to-point integration between these various systems is not feasible; hence, APIs become the primary means of communication between these disparate systems. A clean architectural approach is the one suggested by the agile integration concept. APIs are central to this concept, which allow data to be shared securely between internal and external systems. The opening of APIs enables a company to provide uniform data and transaction interfaces to internal and external developers, partners, and customers, for improved data access and control of remote resources. By providing well-defined APIs, developers can use data in a programmatic manner; e.g., app developers can get access to IoT devices data without worrying about the underlying hardware interfaces. Considering the importance of APIs for IoT, it’s imperative for an organization to manage these APIs effectively. In fact, APIs have been called a fundamental enabler of IoT however, without an effective API Management solution, API sprawl can easily lead to catastrophe.

Continue reading “Taking Control of your IoT APIs”