No
Yes
View More
View Less
Working...
Close
OK
Cancel
Confirm
System Message
Delete
Schedule
An unknown error has occurred and your request could not be completed. Please contact support.
Scheduled
Wait Listed
Personal Calendar
Speaking
Conference Event
Meeting
Interest
There aren't any available sessions at this time.
Conflict Found
This session is already scheduled at another time. Would you like to...
Loading...
Please enter a maximum of {0} characters.
{0} remaining of {1} character maximum.
Please enter a maximum of {0} words.
{0} remaining of {1} word maximum.
must be 50 characters or less.
must be 40 characters or less.
Session summary
We were unable to load the map image.
This has not yet been assigned to a map.
Search Catalog
Reply
Replies ()
Search
New Post
Microblog
Microblog Thread
Post Reply
Post
Your session timed out.
Red Hat Summit 2017

S102365 - The future Red Hat Middleware portfolio: Stacks and services and solutions

Session Speakers
Session description

Over the last five years or more—since before the dawn of Red Hat OpenShift—Red Hat JBoss has brought all our middleware products to the cloud. Since Red Hat OpenShift, that effort has redoubled, and with the advent of Red Hat OpenShift 3 (based around Linux containers and Kubernetes), we have been considering what needs to happen beyond just helping our existing products work well in the cloud.

There will be a layer of core middleware services that developers can use to build applications, sitting between (or within) the Linux container and middleware layers. We're refactoring existing products to core services, such as messaging, security, transactions, and cacheing on (or in) Red Hat OpenShift. We're also considering reimplementing existing products to use these core services, though that's likely to be on a case-by-case basis.

In this presentation we'll look at where we've been and where we're going with middleware services within Red Hat OpenShift; what changes are necessary within our middleware products and projects to support the new immutable architectures approach behind Linux containers and Kubernetes; and consider how this impacts developers interested in enterprise microservices—especially those who don't necessarily want to code exclusively in Java.

Additional information
Integration, Business automation, Application platforms
Breakout session
45 minutes
Session schedule