VMware's vFabric Cloud Application Platform focuses on providing a flexible, scalable infrastructure for modern applications, an empowered and secure mobile workforce, and faster time-to-market. The vFabric Suite offers a lightweight Java application server, data caching, database, and messaging solutions with cloud-friendly licensing designed to meet the needs of developing applications for elastic cloud environments in a cost-effective manner. It aims to provide a modern approach to application infrastructure that allows for both modernizing existing applications and building new applications optimized for cloud delivery, developer productivity, and changing data and application trends.
2. VMware’s Three Strategic Focus Areas
Flexible, Scalable, Efficient Infrastructure
Faster Time-to-Market for Modern Applications
Empowered, Secure Mobile Workforce
4. New apps aren’t being built with legacy middleware…
Not a single one of our startups
uses Oracle. I think the clock is
really ticking…. they've `cranked up
the maintenance fees.
- Marc Andreesen, 9/28/11
Source: San Francisco Chronicle
vfabric.co/chronicle
5. … because customers are choosing open source
“Java application servers
have become commoditized.”
vfabric.co/infoworld
6. Analysts recommend lean application infrastructure…
Too many clients spend far too much time and effort trying to find the
products with the most features. Lean shops look for just enough, no more.“ ”
7. … and open source embodies lean application infrastructure
“Apache Tomcat will satisfy the deployment
requirements of most Java web applications.”
JULY15, 2011
Stop Wasting Money On WebLogic, WebSphere,
And JBoss Application Servers
BY MIKE GUALTIERI
vfabric.co/forrester
8. Tomcat and other servlet containers are well within
the "good enough" threshold.
Through 2017, at least 70% of new enterprise Java
applications will be deployed on an open-source Java
application server.
vfabric.co/gartner
9. 9
New applications tend to be built on Apache Tomcat
Source: ZeroTurnaround Developer Productivity Report 2012
vfabric.co/zeroturnaround
10. Application Trends Driving Change in IT
Cloud Delivery
• Offered “as-a-Service”
• Virtualization
Developer Productivity
New application frameworks driving
increase in application development
New Application Types
• Mobile, SaaS, social
• Apps released early and often
Data Changes
• Web orientation drives exponential
data volumes
• Reduced latency and new types of data
11. The Move to Modern Frameworks
Assembly
High-level/
Structured
Object-
oriented
Design
Patterns
Time
Abstraction
Modern
Frameworks
Abstraction Increases Over Time
Modern Frameworks
• Productivity
• Portability
Enterprise Java Apps use Spring
>50%
Over half of enterprise Java apps
running on WebSphere and WebLogic
use Spring.
Spring Developers
>2.5M
Source: Gartner, Evans Data
12. New Era Requires a Shift: Elasticity from Apps to Data
Access data through in-memory
data fabric maximize data scalability
Store app state in elastic data cache
maximize app scalability
Develop using frameworks
agile apps decoupled from middleware
Use cloud-friendly messaging protocols
enable flexible app integration
Leverage runtimes optimized for vSphere
provision in seconds
14. vFabric Suite: A Modern Approach to Application Infrastructure
Lightweight, simplicity
• Commercial Tomcat as core container
• Optimized for vSphere and Spring
Licensed for virtual and cloud
environments
• Per VM pricing
• Average use licensing
• Fluid licensing
Modernize Today’s Applications,
Build for Tomorrow’s
vfabric.co
15. 15
vFabric tc Server: Lightweight Java Application Server
Efficient, lean, fit-to-purpose runtime platform
Lower cost and complexity
Enterprise capabilities on Apache Tomcat-compatible base
vfabric.co/tcserver
16. 16
vFabric tc Server: Small Disk Footprint
0
500
1000
1500
2000
2500
tc Server 2.6
Standard Edition
IBM WebSphere
8.0.1
Oracle WebLogic
12c
Redhat Jboss EAP
5.1.2
Size on disk - one server instance (MB)
vfabric.co/tcserver
17. 17
vFabric tc Server: Low Memory Footprint
0
50
100
150
200
250
300
tc Server 2.6
Standard Edition
IBM WebSphere
8.0.1
Oracle WebLogic
12c
Redhat Jboss EAP
5.1.2
Memory committed at startup (MB)
vfabric.co/tcserver
18. vFabric SQLFire: Scalability at the Data Tier
Speed: In-memory, distributed SQL database.
Scale: More scalable design than traditional RDBMS.
SQL: Familiar SQL interface, accessible from Java and C#.
vfabric.co/sqlfire
19. 19
vFabric RabbitMQ: Modern Messaging for the Cloud
Cloud-scale Message Bus
RabbitMQ Message Broker
AMQP, HTTP, HTTPS, STOMP, SMTP, XMPP …
Point -to-point and pub-sub
Virtual hosts, dynamic configuration
Cloud Services DevicesApplications
vfabric.co/rabbitmq
20. 20
Application Blueprint
Out of the box blueprints for vFabric Suite
OS OS
OS OS
vFabric Application Director: Automated Application Deployment
Application Services
OS OS
OS OS
22. … then drill into code to find cause of slow transactions
23. 23
The Cloud Requires a Shift in Licensing Philosophy
Cloud Requirement Legacy Licensing
vFabric Suite
Cloud Licensing
1 Apps deployed on
virtual infrastructure
• Per-core pricing with
complex physical
hardware “power factors”
• Per-VM Pricing for
hardware independence
2
Web orientation drives
highly variable
workloads
• Peak-use licensing
• Budget wasted on rarely-
used licenses
• Average-use licensing
• No budget waste
3 “Deploy first, ask
questions later”
• Server-specific licenses
• Cannot re-use across
different server types
• Fluid Licensing
• Re-use licenses across
different types of servers
vfabric.co/pricing
24. 24
vFabric Suite Advanced Competitive Pricing: Typical Scenario
VMs Cores (Estimated)
Application Server 100 86
Data Cache 100 86
Database Server 25 22
Web Server 25 22
Message Broker 25 22
Monitoring (same at total) 275 228
Total 275 238
25. 25
vFabric Suite: Priced for Wide Adoption
15%
Cost of VMware vFabric
compared to
Oracle WebLogic
55%
Cost of VMware vFabric
compared to
IBM WebSphere
&
26. 26
vFabric Suite: Priced for Wide Adoption
Product Map & Costs IBM Oracle VMware
Product Price Per Core Product Price Per Core Product Price Per VM
Product Family IBM WebSphere $ - Oracle WebLogic Suite $ 22,500 VMware vFabric Suite Advanced $ 2,500
Application Server WebSphere Application Server $ 2,873 WebLogic Server $ - vFabric tc Server 1
$ -
Data Cache WebSphere eXtreme Scale $ 8,633 Coherence Enterprise Edition $ - vFabric GemFire App Cache Node $ -
Database DB2 Express Edition $ 3,165 MySQL Enterprise Edition $ 625 vFabric SQLFire Professional $ -
Web Server WebSphere HTTP Server 2
$ - Web Tier $ - vFabric Web Server $ -
Message Broker WebSphere MQ $ 4,273 WebLogic Server JMS $ - vFabric RabbitMQ $ -
Monitoring Tivoli Monitoring $ 552 Enterprise Manager $ - vFabric Hyperic $ -
Pricing Metric Cores Cores VMs
Product Price - Subtotal $ 331,603 $ 1,288,750 $ 195,000
27. 27
“When we took to the sky, forty years ago, I don’t think anyone had
the vision that we would be using the cloud to actually deliver our
product, deliver information, and help us lower our cost.”
Ginger Hardage, SVP Culture and Communications
vFabric powers Southwest.com, support the majority of
Southwest Airlines revenue
Southwest Airlines – Application Modernization & Data Fabric
Challenge
Growth led to Southwest.com
performance challenges during
peaks like Super Bowl and fare
sale ads.
Needed a more elastic
architecture to dynamically
scale their environments and
maintain their legendary
customer service reputation..
Solution
Using tc Server, Apache Web
Server, GemFire, and vSphere,
Southwest built an efficient,
agile, and scalable architecture
to handle peak performance
requirements of their virtualized
application and data services.
Results
Boosted performance on one of the
travel industry’s largest websites.
Enabled expansion with new mobile
platform and creation of new
employee tools.
Agile architecture shortened time
required to integrate newly acquired
ATA into Southwest.com passenger
reservations & bookings services.
vfabric.co/southwest
To address this challenge, VMware is focused on three core solution areas in IT:
How best to evolve the infrastructure to support this new world,
Changes in application development to speed time-to-market for business-critical applications, that take advantage of this new world,
And a new way of approaching end-user computing, to increase user satisfaction.
<click>
Let’s begin by exploring the evolution of infrastructure.
http://online.wsj.com/article/SB10001424053111903480904576512250915629460.html
First we need to ask, Why the focus on scalability?
Because every business is a software business. If your apps can’t scale, your business can’t scale.
Source: http://www.sfgate.com/cgi-bin/article.cgi?f=/g/a/2011/09/28/businessinsiderboxnet-2011-9.DTL
IBM WebSphere and Oracle WebLogic are becoming the new mainframes.
Just like mainframes aren't going away anytime soon, neither are WebSphere or WebLogic.
And just like mainframes, the sole reason for WebSphere and WebLogic are to main existing applications -- not to build new ones.
Source: http://www.infoworld.com/t/java-programming/still-dont-think-open-source-hurts-commercial-software-guess-again-184168
The application server market has fundamentally changed: even in the most conservative enterprise new applications are being built on Open Source Apache Tomcat, not traditional heavyweight application servers.
Customers have discovered they don’t need to pay $45,000 per CPU when Tomcat is a better solution.
Recommended Forrester Reading:
Lean Software Is Agile, Fit-To-Purpose, And Efficient; Dec 12 2008
Lean: The New Business Technology Imperative, Sep 29 2009
There was an arms race in the application server world a decade ago: implement as many features and standards as possible.
But winning the checkbox battle means that you lose the efficiency war.
All those features and spec implementations come at a cost:
They require a good chunk of memory and disk. For example, hello world on a traditional app server might require half a gif, versus 50 MB for a lean, open source solution.
This in turn means larger VMs, fewer VMs on a vSphere host, and ultimately more costs for hardware, rack space, real estate, and power.
It also hurts your ability to scale elastically, since you have fewer physical hosts on which to scale out.
Also, they are time-consuming to learn, setup, and maintain, which hurts time to market.
Source: http://blogs.forrester.com/mike_gualtieri/11-07-15-stop_wasting_money_on_weblogic_websphere_and_jboss_application_servers
Instagram is a great example of how application infrastructure has changed forever: they recently shared the architecture that enabled them to scale to 30 million users – an open source database, an open source framework, an open source in-memory technology. Five years ago that would have been built on Oracle, but that just isn’t the case any longer. Clearly Instagram is at the extreme end as a consumer application, but the enterprise has taken note.
This year, over 1800 respondents shared their take on “the developer life” with us, with 1100 Java-focused surveys completed.
Source: http://zeroturnaround.com/blog/developer-productivity-report-2012-java-tools-tech-devs-and-data/
There is a set of technical themes that are driving this disruption in application architectures.
First: the way that applications are being built is completely different: rather than being written at a very low level, they are increasingly written with Frameworks. This is essentially a higher level paradigm, one that focuses on simplicity and component reuse. In the Java world, more than 50% of ALL the java applications running today are written with Spring. But it is not limited to Java: emerging languages are all based on framework – Rails for Ruby, Node.js for Java Script, Grails, etc
Second, the types of applications being written today are very different than they were 5-7 years ago. As we look out at our customers’ application portfolios, the majority of applications are driven by initiatives around mobile, SaaS and social. The development process for these kinds of apps is also very different: rather than being 9 month dev cycles, they tend to have rapid iterations allowed by this new paradigm: they are developed, tweaked, deployed, tweaked, deployed, etc. This has implications for the kinds of technologies being used.
Third: data. This is a wholesale change. These mobile, SaaS and social apps put pressures on the database-only approach to data management, and many instances are themselves the cause of the massive spike in data volumes. Concepts like low latency / elasticity, multi-cloud are critical to this new generation of apps. And above all, the sheer quantify of data that they are dealing with is a real challenge.
Finally, whether app teams like it or not, many organizations have a virtual-first policy for new applications. While we have certainly proven that any app can be virtualized, if you know your app will be running on virtual infra there are opportunities to architect it to leverage this powerful construct.
Together, these trends are driving a real transition in the technologies being used to build, run and manage applications.
--
We have seen a huge transition in the way that applications are built today: the development framework has innovated to the point that most of the heavy lifting is done in the framework – such as Spring Integration – meaning that your applications really only need a simple place to execute logic. And that means simple and open source have risen to the fore.
The framework is the surface area for development today, not the app server.
Why frameworks?
In fact what we see very consistently is that much of this transition can be traced to the adoption of the Spring Framework, which enables applications to run on a simple container rather being tied to a large JEE container. It is no coincidence that the rise of Spring and the rise of Tomcat have largely paralleled each other.
And this selection of Spring then drives a series of follow-on implications and architectures, with an emphasis on the simplest possible components designed with scale-out in mind, to the point that this architecture is the one we see over and over again in our Enterprise customers:
Once using Spring, Tomcat comes next
From there, organizations think about session state management outside of the container
It also coincides with a shift in messaging technologies, typically to something open source
And gives rise to the use of in-memory at the data tier
This really reflects the maturation of the web era of application infrastructure and we see it over and over again.
vFabric 5 is really focused on those 2 challenges:
Application platform optimized for both the Spring Framework that is used by the majority of the world’s Java developers
Licensed for the realities of the modern datacenter
And as I’ll cover in a moment, containing the core components of our PaaS offering, thereby creating a pathway for our customers to the PaaS era.
Developer Efficiency
Familiar Spring + Tomcat experience
Agile Spring development experience via STS
Enhanced build process via Maven plugin
Operational Control through Hyperic
Performance & SLA management of Spring apps
Application provisioning and server administration
Rich alert definition, workflows, and control actions
Group availability & event dashboards
Secure unidirectional agent communications
Deployment Flexibility
Lean server (10 MB) ideal for virtual environments
Template-driven server instance creation
Integrated experience with VMware environments
Open, secure API for all operations
There is a huge shift underway in data technologies: in the previous technology generation, the canonical app was an enterprise app like SAP, being accessed by a few hundred users. Today, the canonical application is likely to be accessed by millions of users around the world and on their mobile device. This is forcing customers to adopt an in-memory approach as the only way to scale the data tier.
And that is why we include vFabric App Director in the vFabric Suite, which is about leveraging the construct of a VM to automate the deployment of application infrastructure. There is a huge amount of interest in Application Director for automation, enabling a user to create reusable architectural Blueprints to simplify the deployment of vFabric components on vSphere.