In the mid 90s, Bill Gates famously said that “banking is necessary, banks are not.” There is certainly a lot of truth in this statement. We all need banking services in some shape or form. But who delivers these services to us is secondary. In fact, Accenture concluded in a study conducted in 2016 asking over 30,000 people in 18 countries that if the tech titans like Google, Amazon, or Facebook would offer such services, 31% of the respondents would switch to them. This clearly imposes a significant threat on traditional banking institutions.
Another challenge that banks are facing worldwide are the increasing demands for regulatory compliance with respect to openness. Such regulations include, for instance, Payment Services Directive 2 (PSD2) in Europe, the Amendment Bill to Japanese Banking Law in Japan, the National Payments Corporation of India (NPCI) with the Unified Payment Interface, UK’s Open Banking standard by the Competition and Markets Authority (CMA), or the Open Banking Regime by Australia’s Federal Government. Banks approach these regulatory challenges in many different ways. Some see it as a serious business threat and only do the bare minimum for compliance; others see it as an opportunity and with smart investment start building banking platforms for the future.
Our suggestion for building the banking platform of the future resides on the principles of agile integration, which is an architectural approach centered around application programming interfaces (APIs) and API management. At its core, agile integration resides on the three pillars: distributed integration for greater flexibility, containers for the ability to scale better, and managed APIs for re-usability and hence speed. We described the details in an earlier post.
Continue reading “The Role of Agile Integration in Open Banking”
Earlier this months at the Gartner ITxpo event, Massimo Pezzini presented the challenges that must be addressed by a pervasive enterprise integration strategy. In summary there are four types of hybrid challenges (see Massimo’s diagram below).
Continue reading “How to Address the Challenges of a Pervasive Integration Strategy”
Today is a special day for the 3scale team at Red Hat. It’s been just 10 short months since the company joined Red Hat in the summer of last year and there has been a buzz of activity for the entire time.
One of the biggest new goals was to add a fully on premise version of the 3scale API Management product to the line up alongside the existing Software as a Service (SaaS) version. Hence the team is very happy to announce the availability of that new version which is now generally available. Get started looking at 3scale’s customer portal page.
Launching the on-premise version is special for two reasons. First, because increasing numbers of customers are now running large numbers of public and private APIs – often deep in their internal infrastructure. Deploying API Management in their own data center or in a cloud environment they own is often a key part of succeeding. Second, it is special because of the way on-premise is being delivered. Specifically the new product is shipping entirely on Red Hat’s powerful container management platform, OpenShift.
Continue reading “Go Anywhere API Management: 3scale API Management adds a Fully Containerized On-Premises Version”
Updated and enhanced integration services are now available on Red Hat OpenShift. A containerized, formatted version of Red Hat JBoss Fuse 6.3 is now available for simplified deployments on OpenShift instances.
Technology is shifting so rapidly — from cloud-based architectures, Internet of Things and a variety of devices for interaction, new data streams, and mobile apps, to name a few — that organizations have to be able to create and deploy applications and process data quickly. Traditional, monolithic systems and top-heavy ESB-style integration approaches tend to be too slow and rigid to enable this level rapid innovation.
That is where an agile integration framework like JBoss Fuse can be a foundational element in your IT and digital strategy. Agile integration has three core capabilities: distributed integration, containers, and an API-based architecture.
- JBoss Fuse uses the lightweight distributed integration patterns of the underlying Apache Camel project.
- As part of the JBoss middleware services on OpenShift, JBoss Fuse is available for rapid deployment within container and cloud environments. Red Hat OpenShift is based on Docker and Kubernetes. Container architectures allow developers to build and integrate traditional and microservices-based applications at scale quickly.
- JBoss Fuse can be used together with Red Hat 3scale API Management Platform as an engine to develop and deploy APIs, both internally to development groups and externally for customer and partner ecosystems.
Integration technologies help organizations build on their existing infrastructures even as they pivot to new cloud-based and service-based architectures.
Features (and Benefits) at a Glance
- Spring Boot support
- Custom-developed, containerized applications based on Apache Camel 2.18
- Integration with Hystrix and Zipkin microservices frameworks
- An optimized integration environment for microservices applications on Red Hat OpenShift
- Path to transition off existing Apache Karaf-based applications to cloud architectures
- Consistent hybrid integration platform across their enterprise
Happy Friday, everyone!
I’ve still been running through year-end retrospectives and new year predictions, and I haven’t hit on a theme yet. (The character of 2017 is still enigmatic.) As always, though, there are lots of good things on the interwebz, and this week covers the gamut — containers, big data, machine learning, and Alexa.
Continue reading “Five Links: A Little Bit of This Edition”
For more than 10 years, Red Hat JBoss Middleware has been a successful business that deeply represented the Red Hat DNA: open source software. We expanded our product portfolio with projects created and imagined by the open source community; we decided to support other projects with contributors; and we also opened the source of technologies we acquired. Somewhere along the way, Linux containers, Kubernetes, and docker happened which made us realize that containerization of applications is the base for your next 20 years. The caveat in this is that a platform is only as important as the applications you run on top of it. In other words, a platform not running applications is not realizing its value. With that in mind, we made an important decision and investment to evolve our application portfolio in similar ways that we ask our customers to do to theirs: let’s take our Red Hat JBoss Middleware products, commonly deployed on Linux and Windows machines, and make them available as containerized deployments.
With the announcement of the availability of JBoss Data Virtualization for OpenShift we now have 100 percent of our Red Hat JBoss Middleware runtime portfolio containerized and available in Red Hat OpenShift, an enterprise-ready Kubernetes distribution with value-added capabilities that go from deploying your already packaged container images, to delivering a DevOps pipeline for an iterative development process.
Continue reading “Bringing Containerized Services and DevOps Closer to (Your) Reality”
This series started with the statement, what do you mean by “Can’t ignore the stack anymore?”
When your background is application development, you have spent many hours, days and years perfecting your craft. You have not only mastered languages and concepts, you have made it a point to learn to make good architectural decisions when pulling together the applications you develop.
The problem is, we tend to ignore the stack we are working on as much as we can. Well it’s time that we as application developers broadened our horizons a bit, expanding our understanding of the stack we work on with the introduction of Cloud, Platform As A Service (PaaS) and containers to our toolboxes.
Our tour of your Cloud stack continues, from our previous article in this series where we talked about our PaaS interface for our application delivery, onto how open interoperability is critical to the success of our Cloud stack.
Continue reading “App Dev Cloud Stack – Open interoperability critical to success”
DevOps methodologies are core to a (modern) IT environment because they focus on strategic business demands: resilient design, rapid scale, and reliable service delivery. That last characteristic is the critical for effective DevOps environments.
The goal is for you to move through the total dev stack, as fast as your development team can code. Our new video shows how a Java app goes from being developed on an OpenShift container to launching on a production cloud instance in under five minutes.
Continue reading “Containers, cloud, and Java apps: A new video on development stacks”
A little more than two years ago, we announced Red Hat’s “xPaaS” initiative to provide Red Hat JBoss Middleware on OpenShift and introduce a new way of building and deploying enterprise applications. Our efforts in executing against that vision and roadmap have entailed a lot of work and have been very exciting.
Continue reading “Red Hat announces availability of containerized middleware capabilities on OpenShift”