As they say, Red Hat Summit is for developers. (And also architects, IT managers, operations, CTOs … it’s pretty diverse.) There year, there are several tracks dedicated to application development, from slightly different perspectives:
- Application development (focusing on things like developer tools, labs, microservices)
- Application platforms (focusing on things like legacy migrations, containers, microservices, Java)
- Application delivery (focusing on things like DevOps, containers, integration patterns and Camel)
There are almost 350 different sessions, labs, and demos at Red Hat Summit, and over 100 just on application development and delivery — and they cover an amazing variety of topics. The ones that grabbed my attention most seem to be clustered around microservices (there ain’t no service like a microservice cause a microservice don’t stop!), but that goes back to my fascination with architecture and the underlying design of things. Check out the entire catalog, and you can create your own best-of list.
Thursday, 11:30, 151B
There are two very cool projects covered here: WIldfly Swarm, which is a JBoss / Wildfly off-shoot focusing on fat jars or tiny containerized apps and Eclipse Microprofile, which is essentially a Java spec for microservices. Both of these use lightweight apps in flexible architectures, while leveraging the power (and familiarity) of Java.
Wednesday, 4:30, 153C
This is the real life application of microservices (something frequently called a unicorn because of its not-very-real-life concept). Practical applications are very appealing, and this looks at both the pluses and minuses of using microservices for a hosted customer service.
Wednesday, 11:30, 102B
There is a lot of buzz around the watercooler for this one because of the introduction of OpenShift Application Runtimes — a container-based platform for running a variety of different runtimes, including MicroProfile, Vert.x, and Springboot.
Thursday, 3:30, 151A
So how many things are reactive? A lot. A lot of things. This session will break down what “reactive” means (and its many meanings and contexts) and what that means practically for any app that has to interact with something else, whether microservices or any architecture.
Thursday, 10:15, 153B
A lot of CTOs just felt their palms start sweating at this title. For a lot of organizations, any kind of “digital transformation” feels a lot less exciting and a lot more terrifying. Legacy apps are working and are generally tightly intertwined with the core operations of an organization … so how would you begin to unravel that, if you even want to?
Tuesday, 4:30, 101
Most of the sessions I was drawn to focused on architecture, but this lightning talk hits two other critical factors for any infrastructure: process and platform. This looks at how technology can support process (containers and devops) and how platforms can support both existing and cloud-native applictions (Java and MicroProfile).