Summit Notes: Tuesday Morning General Session

If you missed it, the keynote speeches are available on the Summit page or on YouTube.

“You don’t need to focus on technology. You need to empower your developers.”

There are certain patterns in the middleware / application development tracks for Red Hat Summit this year, and they revolve a lot around microservices. That makes a certain kind of sense (microservices are the new hotness in app development), but it’s also reflective of a larger current in technology, a continuing push toward … something.

In his opening keynote, Red Hat EVP Paul Cormier noted that one of the themes of Summit 2016 was “dev and ops coming together through common architectures, processes, and platforms.” This echoes major trends in technology — DevOps and architectures, process, and platform as a unifying IT strategy — and yet none of these concepts are really new. Two decades ago, there were developers and operations, there was enterprise architecture, application platforms, and internal processes. So what’s new and what is bringing the urgency now?

I think the difference comes down to speed (and eventually differences in degree become differences in kind). Twenty years ago, an application was released yearly, sometimes even every couple of years. A patch or security update could take a few months to move in the pipeline from development to testing to production.

Now customers expect patches for security vulnerabilities within hours of them being detected, and the expanding number of applications (from consumer mobile apps to internal systems to IoT devices) means that enterprises have potentially dozens of touchpoints and hundreds of services to maintain.

The “modern” part of modern application development isn’t in the app — it’s in the speed.

This year’s Summit kicked off with three interlocking demos, each showing the different paths and progressions that an IT environment will face as they juggle modernizing existing applications and creating new ones within a heterogeneous (and dynamically changing) ecosystem.

 Lifting and Shifting (Windup)

Continue reading “Summit Notes: Tuesday Morning General Session”

Eclipse MicroProfile continues its growth in the market

Organizations that have already embarked or are thinking about starting a digital transformation journey are assessing and looking for ways to leverage their Java EE expertise. IT development and operations have built Java expertise over years, and there is a challenge to balance their existing skill base with new digitally transformative technologies, such as microservices, APIs, container-based architectures, and reactive programming. Eclipse MicroProfile is an open source project and one of those digitally transformative technologies that enables and optimizes the development of microservices — using familiar Java EE technologies and APIs.

You can think of MicroProfile as minimal standard profile for Java microservices. As with Java EE, MicroProfile implementations across different vendors are fully interoperable.

MicroProfile is supported in WildFly Swarm on the recently announced Red Hat OpenShift Application Runtimes, our polyglot runtime platform powered by OpenShift, Kubernetes, and OpenStack. This delivers on the goal of simplifying the inherent complexity of developing cloud native applications.

There are a lot of reasons to begin adopting MicroProfile:

  • Open source, of course
  • Agility in developing microservices
  • Ability to leverage innovation
  • Architectural interoperability across different vendor offerings
  • No vendor lock-in
  • Fast learning curve for Java EE users (Java EE users can leverage their knowledge when using MicroProfile)
  • Ability to run on Red Hat OpenShift Application Runtimes 

Since MicroProfile was announced in June 2016, a lot has happened.  MicroProfile v 1.0 was released on September 19, 2016. Its implementation interoperability was demonstrated on November 2016 at Devoxx, where Red Hat, IBM, Tomitribe, and Payara demoed a unified web application with underlying microservices which had been developed separately by each vendor using MicroProfile. In addition, MicroProfile became part of the Eclipse Foundation as an incubation project back in December 14, 2016. New members have joined MicroProfile, such as SOUJava, Hazelcast, Fujitsu, Hammock, and kumuluzEE (the complete list of members can be found here).

Future releases of MicroProfile will build upon the existing foundation with organic growth by adding configuration, security, health check, and fault tolerance APIs, as well as adding support for later versions of CDI, JAX-RS, and JSON-P. The MicroProfile open source project plans to put out releases on an agile schedule and based on feedback from the open source community, which is accessible to everyone. Join the conversation and check out the MicroProfile site.

Announcing the Alpha release of Red Hat OpenShift Application Runtimes

Today Red Hat announced the alpha release of Red Hat OpenShift Application Runtimes (RHOAR). This is the first of many articles on the subject that will be published on the JBoss Middleware blog.

So what is RHOAR?

RHOAR provides application developers with a variety of application runtimes running on the OpenShift Container Platform. Specifically, the following application runtimes will be included in RHOAR:

  • Red Hat JBoss Enterprise Application Platform (EAP) – existing Java EE / Spring apps.
  • WildFly Swarm running MicroProfile – Java EE centric MSA
  • Spring Boot / Cloud – Spring centric MSA
  • Vert.x – greenfield reactive Java
  • Node.js – greenfield reactive JavaScript

Continue reading “Announcing the Alpha release of Red Hat OpenShift Application Runtimes”

Accelerating Time To Value In The New Digital Economy

Cross-posted from the Red Hat Services Speak blog.

Today, most organizations have significant internal datasets and digital services. These resources have the potential to be converted into new revenue streams by securely exposing them to customers and partners as web services. The availability of a number of open source web service frameworks, has meant that it has never been easier to develop RESTful APIs and expose these resources to customers. This allows organizations to validate an idea or hypothesis and capture customer feedback in a matter of weeks or possibly even days.

Source: https://upload.wikimedia.org/wikipedia/commons/f/f9/Open-APIs-v5.png

While the internet has leveled the playing field in delivering new products and services, paving the way for small companies or startups to compete and disrupt far larger and better funded organizations, it has also meant that competitors can bring their own offerings to market more quickly than ever before. Developing a sustained competitive advantage for products and services has never been more important.

Every successful web services organization has one thing in common. They each adopt an agile approach to software development and have an obsessive focus on customer centricity. This allows them to significantly reduce the time it takes to incorporate customer feedback into their products and services. Reducing the time from months to weeks or days means they can often increase the feedback effect by a factor of 10x. The ability to reduce the time from idea to customer validation will be one of the greatest contributors to help organizations sustain a defendable competitive advantage.

Organizations that grew up as digital service providers have already figured out how to securely and reliably provide services over the internet, but what about organizations that are going through digital transformation and entering new territory? Developing and sharing web services outside of an organization requires significant additional effort compared to simply exposing services internally. It is necessary to increase the focus on security, scalability, reliability, track consumption, access control, ensure Quality of Service (QoS) and subsequently bill customers. Building this capability from scratch requires significant heavy lifting and resources, resources that would be better served developing web services rather than a management platform to support them. To this end, most organizations adopt an API management platform to remove this burden and allow their teams to focus on what’s truly important, developing digital services to meet the needs of their customers.

Back in June 2016, Red Hat acquired 3Scale, a leading provider of API management. In addition to addressing the challenges I’ve highlighted around API management, 3Scale also provides valuable data analytics that can be used to show how customers are using each service. This further amplifies the feedback signal from customers and allows organizations to be even more customer centric.

Is your organization going through a process of digital transformation? Are you exploring creating web services to expose datasets and digital services to customers and partners? Do you need help developing an API management strategy and platform to support your business? If so, please contact the Red Hat Consulting team so we can help accelerate your journey towards open innovation.

Five Links: Fun and Games Edition

Happy Friday, everyone.

As we kick off spring break season, let’s look at something a little lighter and happier: the gaming side of technology. Consumer design can be a huge driver even for enterprise technology; the simple UX of Apple products is now influencing design and experience expectations for backend systems. From nostalgia games to astronomical artwork, there is a lot of interesting stuff going on in the world. One of my favorite lines from Graceland (seriously, Paul Simon rocks, people): “These are the days of miracles and wonder.”

Continue reading “Five Links: Fun and Games Edition”

Five Links: Band of Brothers Edition

Happy Friday, everyone.

Red Hat has a lot of corporate blogs (worth reading!), but a huge part of our culture as a company is collaboration and meritocracy. As in … letting our opinions be known. There’s a reason we actually made a t-shirt to commemorate our corporation-wide mailing list.

happy-friday

From Pinterest

A lot of Red Hatters have personal blogs (or active LinkedIn postings) precisely because of the value that we as a group place on transparency, defending ideas, and innovation.

This week, I want to highlight some of the blogs by Red Hatters that I’ve read recently. I’m not even going to call this a “top 5,” because we have a lot of prolific and interesting writers on a million different topics. These are a random sampling of the blogs that I hit periodically.

Continue reading “Five Links: Band of Brothers Edition”

Five Links: Pattern Recognition Edition

Happy Friday, everyone.

When I was a reporter in Livingston, Montana, I wrote a story about a massive infrastructure campaign that was just kicking off — new sewer and water lines across town, changing traffic flows and redesigning streets, new green spaces and public art. I interviewed the primary architect, and he told me that the designs were influenced by A Pattern Language, published in 1977. That book has fascinated me; from the placement of a single window to the layout of an entire central business district, it breaks down the patterns of human behavior and then analyzes design techniques that best reinforce the desired patterns for a given space. It doesn’t say what should be done; it simply uses patterns to say if you want to accomplish Goal A, use Design Technique B.

In a roundabout way, this week’s series of links look at patterns and how they influence behavior.

friday

 

Continue reading “Five Links: Pattern Recognition Edition”

Ultra Low Latency API Management for Microservices with Red Hat 3scale

In this article, we provide a solution that enables almost latency free API management for Java-based microservices APIs. We build on Manfred Bortenschlager’s white paper Achieving Enterprise Agility With Microservices And API Management. We provide a practical solution for adding the management layer Manfred outlines to internal microservice-to-microservice API calls.

API Management and Microservices

Figure 1 – a typical microservices architecture with depictions of externally and internally consumable microservices

image00

In the white paper Manfred describes a typical microservices architecture consisting of:

  • A perimeter service layer that is typically implemented by an API gateway which manages and secures components that follow the backend for frontend (BFF) pattern. The perimeter service exposes APIs to external consumers.
  • Internal microservices that are clustered into functional elements and communicate via APIs.

The most common and most decoupled way to achieve API management is through deployment of API gateways on the API provider’s infrastructure. These gateways act as traffic controllers which authenticate, authorize, and report on API traffic to the 3scale API Management Platform. These extensive management features are achievable with very low latency overhead through our caching and asynchronous architectural features. Additionally the gateways provide excellent routing and security protections such as defense against DDoS attacks and more.

Continue reading “Ultra Low Latency API Management for Microservices with Red Hat 3scale”

Data and Architecture: Business Architecture and Capabilities

Does your organization talk about connecting the execution of work to its strategy? Are you building a roadmap on how to get there and achieve desired goals? To help your organization achieve the strategy and goals, model the business architecture by understanding the organization’s strategy, communicating business outcomes, and aligning these outcomes to the appropriate business capabilities.

Business architecture is illustrating what the business does and how the business operates. Gartner defines business capabilities as  “what the business needs to do to achieve the business strategy.” Business architecture uses business capability modeling, to visualize and influence people, processes, and technologies needed to maximize stakeholder value, achieve organizational goals, and execute on the business strategy. This model should map out the future state capabilities needed to support where the business is going over multiple years, as defined by the organization’s strategy.

Continue reading “Data and Architecture: Business Architecture and Capabilities”

APIs Are The New Language of Collaboration

“Survival of the fit,” in Darwinian evolutionary theory, describes the mechanism of natural selection. The biological concept of fitness is defined as reproductive success. But could this also apply to modern business? Sustained growth might be the criterion for fitness in a business context. So why is sustained growth so difficult to achieve? Surprisingly, it is not for the lack of ideas but lack of ability to adapt to change and competition.

The fittest business can quickly innovate and adapt to competition and it can use its core competencies to extend itself in new ways. These organizations are often lean, mean, and learning machines using application programming interfaces (APIs). They are built on a foundation of cloud, mobile, big data analytics and social computing and they are generally connected to the internet of things, to extend and monetize the organization’s core assets for growth and  new value and revenue streams.

Even organizations born in different eras of digital transformation (mobile, internet-based, and client/server) that are successfully using APIs to achieve disruptive growth in their respective industries.

Continue reading “APIs Are The New Language of Collaboration”