Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to xPaaS: The JBoss Way
Similar to xPaaS: The JBoss Way (20)
More from Christina Lin
More from Christina Lin (20)
Recently uploaded
Recently uploaded (20)
xPaaS: The JBoss Way
- 1. XPAAS: THE JBOSS WAY Christina Lin JBoss 技術福音戰士 Oct, 2014
- 9. 兩樣都 很重要
- 10. 應用程式的平台越來越重要
- 11. MIDDLEWARE FOR OPEN HYBRID CLOUD AUTOMATION FOUNDATION JBoss Developer Studio DEVELOPMENT TOOLS INTEGRATION JBoss A-MQ JBoss Fuse JBoss Fuse Service Works JBoss Data Virtualization JBoss EAP JBoss Data Grid JBoss Operations Network MANAGEMENT TOOLS JBoss BPM Suite JBoss BRMS PHYSICA L VIRTUAL PRIVATE PUBLIC
- 12. PLATFORM AS A SERVICE FOR OPEN HYBRID CLOUD PHYSICA L PaaS ADMIN NODENODENODE BROKER BROKER VIRTUAL PRIVATE PUBLIC NODE EAP MySQL Svc1 ... ... APP USER APP DEVELOPER/ DEVOPS Svc2
- 13. xPaaS WHERE MIDDLEWARE MEETS CLOUD +
- 14. Enterprise Apps are Complex App component Virtualization/ Private IaaS App component App component App component App component SaaS App component Phys App component Application App component Public IaaS Public IaaS ON-PREMISE PRIVATE PUBLIC
- 15. PaaS Reduces Work and Risk App component Virtualization/ Private IaaS Application App component App component App component App component SaaS App component Phys App component Private PaaS App component Public IaaS Public PaaS Public IaaS ON-PREMISE PRIVATE PUBLIC
- 16. Reduce More Work with Higher-Level Services App component Virtualization/ Private IaaS Application App component App component App component App component SaaS App component Phys App component Private PaaS App component Public IaaS Public PaaS Public IaaS ON-PREMISE PRIVATE PUBLIC
- 17. JBoss xPaaS Services for OpenShift App component Private PaaS Public PaaS Virtualization/ Private IaaS App component App component App component App component SaaS App component Phys App component Application App component Public IaaS Public IaaS ON-PREMISE PRIVATE PUBLIC
- 18. JBoss xPaaS Services for OpenShift bpmPaaS JBoss BPM Suite aPaaS – JBoss EAP iPaaS JBoss Fuse mPaaS AeroGear+ ON-PREMISE PRIVATE PUBLIC
- 19. ●Red Hat JBoss Enterprise Application Platform cartridge ●No special APIs—just standard enterprise Java™ code ● PaaS UX simplifies deployment, scaling, and updates Application PaaS Application PaaS ON-PREMISE PRIVATE PUBLIC
- 20. Integration PaaS Application PaaS Integration PaaS ●Red Hat JBoss technologies for application, messaging and data integration ●Run integration in public cloud or on-premise ● PaaS UX simplifies connection, route, and queue configurations ON-PREMISE PRIVATE PUBLIC
- 21. ●Create process models using cloud service ● Export to business process management (BPM) platform ● Share process models Application PaaS BPM PaaS BPM PaaS ●Run BPM in cloud or on-premise ●Orchestrate applications and services spanning cloud and on-premise ● PaaS UX simplifies configuration ON-PREMISE PRIVATE PUBLIC
- 22. ●Push notification, security, data encryption, offline, and data synchronization ●Support for native, hybrid, and mobile web apps ●Run backend in public cloud or on premise ●PaaS UX simplifies notification and integration configuration, API development Application PaaS Mobile PaaS Mobile PaaS ON-PREMISE PRIVATE PUBLIC
Editor's Notes
- We're a tech company, and we like to talk about technology. But before dive into any detail,, I like to set some context. What is the technology for? Why do we build it, and why do you buy it? Part, if not all, of the answer is that the business context we operate in—whether we're talking about finance, government, healthcare, retail, whatever—is changing faster than ever. Key differentiators just a few years ago now may be merely table stakes or perhaps not even relevant...
- In particular, what customers expect and demand of us has changed significantly. An this is a “co-evolution” of what technology can do and how that continually recalibrates the customer frame of reference. We highlight three areas where customers are more demanding than ever. First, customers expect business to be more immediate. In the modern era of instant gratification, it's no longer good enough to say “we'll have an answer for your by tomorrow” or “we'll let you know when that's back in stock”. Second, pervasive. For a business to keep a loyal customer, it must be everywhere. The brick-and-mortar store front is not enough, and even online isn't enough; there must be kiosks, mobile apps, integrated offers with partners, etc. Finally, businesses must be more aware. As a customer, I expect a vendor to know about me, to tailor its offering to my preferences and context.
- Ok, if that's the business context we're in, how does IT relate to this. Since it has existed, IT's mission has been to make the business work more efficiently, to better serve customers with faster responsiveness and unique offerings. But in this age of rapidly accelerating demands, the old ways of doing IT have not been able to keep up.
- Add to this the rapid advance of available technologies. One factor in the exponential advance of potential IT capabilities these days is the cloud. In a cloud environment, the speed with which developers can experiment, deploy, and adapt, and the speed with which operations can scale, means that new capabilities that can have dramatic business impact can be brought online more quickly than previously imagined.
- Red Hat recognizes that IT environments are fundamentally heterogeneous and that you don't rip out the old and put in the new overnight. That's why we build everything from the ground up around a technology vision we refer to as open hybrid cloud. It's open in all the ways we've been talking about. It's hybrid in that it recognizes that your IT is some combination of four basic footprints: physical, virtual, private, and public. And it's cloud at your pace in a way and combination that makes sense for your architecture and business.
- Ok, moving up the stack from the parts that are largely the domain of the data center operations guy to the domain of the developer and application architect.
- Let's start with a bit of context. We've watched over the years as various constituencies in enterprise software claim the death of the packaged app and the death of custom, do-it-yourself apps.
- The fact is, they're both crucial. How many of you are using Salesforce.com? Some off-the-shelf apps specific to your industry? How many of you have apps that we're built in house? In a survey conducted last year, Forrester found that among large enterprises, about equal investment was being made in both packaged and custom apps. Neither are going away anytime soon.
- And whether it's 50-50, 60-40, or even much more slanted, the platform on which you run your apps is more important than ever: to give you the development flexibility, integration capability, performance, scalability, and perhaps most importantly, the evolvability of your applications, you need the right layers underneath.
- Many of you are probably familiar with JBoss EAP, the leading open source implementation of the Java EE specs, the thing we refer to affectionately as an “app server”. I don't mean to overwhelm you with this diagram, but middleware consists of a number of other important technologies. Working up from the EAP foundation, we have several different integration technologies—messaging, SOA, and data virt—for different use cases. Up at the automation layer we have business rules management and business process management. A full complement of key middleware technologies for building and integrtation your applications and for automating your decisions and processes.
- We launched OpenShift several years ago, and my colleague XXXXX is covering this more deeply in other sessions today. i OpenShift makes efficient use of containers as “gears”, many of which run on each “node” or VM. Gears can contain different parts of the application—your code, the database, 3rd party services, etc. Resources are automatically allocated and adjusted behind the scenes by a “broker”. The app developer and PaaS admin each have dashboards for interacting with the PaaS, and end users of the PaaS-based apps see what appears like any other Web app.
- So, with all that great middleware, and the great new DevOps paradigm enabled by PaaS, what better thing to do than engineer them together? That's exactly what we're doing with xPaaS. In a strategy we announced last year at JavaOne, we're in the process of rolling out OpenShift-optimized variants of all the JBoss Middleware to create a much more productive and innovative future for enterprise software development. Some middleware products are generally available today. Several are in developer preview now, and the next offerings to be made Generally Available will be JBoss Fuse our Enterprise Service Bus and JBoss A-MQ our enterprise messaging infrastructure, coming later this fall.
- So that's what we're doing with xPaaS at a high level. But what is driving the need? The reality of enterprise applications is that they're complex: they're composed of many components—some new some old—distributed across a variety of stacks and infrastructures. To date, many of the applications that have been built on PaaSes aren't applications that have required the higher-level services that enterprise developers are used to, such as integration, messaging, process orchestration, etc.
- As PaaS gains the attention of enterprise developers wanting and needing to put more complex applications in the cloud, higher-level services become more critical. Our customers, many of which have been developing with JBoss for over a decade, have been asking us to provide more of these high-level capabilities into OpenShift in order to recreate in the cloud the same rich environment they've been used to in their current development.
- What is needed is a coherent, unified PaaS offering that provides these higher level service in a consistent, easy-to-use way. Enter “xPaaS”, where the “x” can mean any of a number of these necessary services—“i” for integration, “bpm”, etc. The idea here is to provide in the cloud, on PaaS, that same rich set of capabilities that enterprise developers have come to expect in enterprise-class middleware.
- Red Hat JBoss xPaaS services for OpenShift is comprehensive suite of enterprise services needed for development and deployment of modern, complex enterprise applications in the cloud. xPaaS is the unifying platform that enables customers to build, deploy, provision and manage modern enterprise applications on bare metal, public and private cloud. A platform that encompasses development and management of end-to-end applications that span web/mobile, process orchestration, and integration. > Built with Jboss Middleware, on OpenShift technology, leveraging our expertise > Delivers a unified management console across cloud and on premise > Provides application builder productivity across all the platform's capabilities}
- The roadmap organizes into 4 main areas—4 “x”s, if you will. Application PaaS, or “aPaaS”. Integration PaaS, or “iPaaS”. Business Process Management Paas, or “bpmPaaS”. And finally, mobile PaaS, or “mPaaS”.
- aPaaS is a foundational component for xPaaS, and we've actually had this in place foralmost two years. This is our JBoss Enterprise Application Platform—the industry's leading open source Java EE app server—packaged as what we call a “cartridge” and available on OpenShift for easy point-and-click configuration and deployment. Practically any component of your complex enterprise application will need to run somewhere on one of the four “footprints”—physical, virtual, private, or public—and have core services like persistence and transactions provided to it. This is the job of the aPaaS layer. The OpenShift EAP cartridge requires nothing special for PaaS; you just take the same code you would have deployed in the traditional manner and run it in the EAP cartridge on OpenShift.
- Integration PaaS, or iPaaS, starts to get into the rich functionality that has to-date not been part of a comprehensive enterprise PaaS offering. JBoss iPaaS is based on the great JBoss Fuse technologies that we obtained as part of our acquisition of FuseSource two years ago. At the core of Fuse is Apache Camel, the best and most widely respected open source integration technology out there. The solution includes a cloud-based interface for configuring integration routes and transformations, a choice of containers for both both cloud and non-cloud endpoints, and reliable messaging based on the JBoss A-MQ broker hosted in the cloud or on-premise. Fuse Fabric technology ties the solution together with a highly available runtime registry and the ability to deploy integration containers remotely. JBoss Fuse and JBoss A-MQ will be generally available later this year on OpenShift Enterprise Also coming to iPaaS is JBoss Data Virtualization. This enables you to create reusable data services so your next-generation applications can leverage your information assets whether on premise or in the cloud.
- The JBoss bpmPaaS service for OpenShift benefits from another great acquisition we did in 2012, Polymita. We've had some great business process technologies as part of the JBoss portfolio for a few years now, with business rules based on the Drools open source project, complex event processing, and basic process management capabilities. Polymita brought some great user experience, business activity monitoring, process simulation, and dynamic data capabilities to the table. Brought together in an OpenShift cartridge and and provisioned through PaaS, business analysts can get up and running in a couple of hours or days—not the weeks or months it took in the old-school world.
- Mobile is our fourth area, and frankly, this one's a bit different from the others. In the aPaaS, iPaaS, and bpmPaaS, there are well-established market categories where Red Hat is already the open source leader, and it's a matter of putting those technologies in the cloud in the right way so that enterprise developer rediscover their comfort zone all ready for them in the cloud. But mobile is much newer as a market category, and the paradigms, APIs, and vendors are much less well established. We ourselves have been experimenting with a number of technologies in this space. The one capability unique to mobile that's drop-dead important and a no-brainer as the first to roll out is push notifications. Push is a nightmare for enterprise developers trying to support mobile clients, and our push abstraction, captured in the AeroGear open source project, goes a long way in taking that pain away. Our first step in the mPaaS area is offer that push capability on OpenShift, and I'm happy to say that that capability is available in developer preview TODAY.
- Just a reminder that the great xPaaS capabilities we've discussed, the combination of Red Hat JBoss Middleware and OpenShift ,is part of a broad portfolio of techologies that allow you to …. The future is open, it's exciting, and it's coming faster than ever. We have a vision, approach, and set of technologies that are unique in the industry, and we'd love to work together with you in all the ways you're innovating to succeed in this exciting new world. Thanks very much, and enjoy the rest of the event!