Choosing a PaaS for the Enterprise
•
2 j'aime•987 vues
The document discusses the business case for using Platform-as-a-Service (PaaS) within enterprises. It outlines the benefits of building applications on a PaaS, such as reducing development costs by 30% and avoiding vendor lock-in. The presentation then discusses characteristics of cloud-optimized applications and examples of common PaaS services. Finally, it provides nine questions enterprises should consider when selecting a PaaS, such as whether it needs to be public or private, and what complementary application services are offered.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (15)
Similaire à Choosing a PaaS for the Enterprise
Similaire à Choosing a PaaS for the Enterprise (20)
Plus de Cloud Elements
Plus de Cloud Elements (20)
Dernier
Dernier (20)
Choosing a PaaS for the Enterprise
- 1. The Business Case for Platform-as- a-Service within the Enterprise Mark Geene CEO & Co-Founder @mgeene Richard Seroter Senior Product Manager @rseroter
- 2. Housekeeping • Two presenters; total of 45 minutes • Your lines have been muted – Please ask questions using the WebEx console – You may experience better call quality via phone audio, compared to web audio 2 confidential Tier3.com
- 3. Agenda • Introduce Today’s Speakers • The Business Case for Platform as a Service • 9 Questions to Help You Choose the Right PaaS for your Enterprise • Special Offers • Q&A 3 confidential Tier3.com
- 4. Today’s Speakers Mark Geene is a Co-founder of Cloud Elements, a company that accelerates the development of cloud computing applications by combining open cloud platforms with reusable integrations (Elements) and cloud-optimized application development services. Richard Seroter is a product manager for Tier 3, a Microsoft MVP, blogger, author, trainer and frequent public speaker. He has deep experience and expertise planning and implementing enterprise IT strategies. 4 confidential Tier3.com
- 5. Title one CLOUD APPS FASTER BUILDING Title two April, 2013 Cloud Elements Confidential 2013
- 6. 5 CHARACTERISTICS OF CLOUD-OPTIMIZED APPLICATIONS Multi-tenancy Self-service provisioning Elastic & metered resource consumption Services-based integration Accessible from any device Cloud Elements Confidential 6
- 7. WHAT IS PLATFORM AS A SERVICE (PaaS)? A cloud-aware application development and deployment environment Abstraction layer between your cloud application and your IaaS Provides elastic scaling of your application 7
- 8. EXAMPLE: PaaS SERVICES Application Data Messaging & Application Runtime Services Queuing Management PaaS Cloud Elements Confidential 8
- 9. BENEFITS OF BUILDING ON A PLATFORM Nearly eliminate deployment and DevOps costs Reduce development cost by 30%+ Avoid IaaS lock-in Cloud Elements Confidential 9
- 10. EVERY PRIVATE CLOUD NEEDS A PaaS Build on a cloud-aware platform ... Productivity Leverage same platform as public cloud providers Portable between private and public Establish a standard set of services Cloud Elements Confidential 10
- 11. PaaS-CENTRIC DESIGN Select Your PaaS first; IaaS Second Architect for strict layer separation Anchor app runtime and data services at the platform tier Loosely couple services between the tiers Cloud Elements Confidential 11
- 12. EXAMPLE: PaaS & IaaS SERVICES Application Data Messaging & Application Runtime Services Queuing Management PaaS Network Elastic Storage Services Compute Units Services IaaS Cloud Elements Confidential 12
- 13. OUR EXPERIENCES WITH PaaS Retail Client (without PaaS): Developed originally on IaaS Migrated from AWS RDS to Private Cloud - weeks Physicians Network Client (with Paas): Migrated to hybrid cloud - less than a day Other Clients: Setup, install, configure, deploy - less than a day Add servers / nodes - less than a minute Real-time application management - no code Cloud Elements Confidential 13
- 14. CLOSING THOUGHTS PaaS-Centric Design Productivity Gains of 30% - 50% Portability Enhanced With An Open PaaS Cloud Elements Confidential 14
- 15. 9 Questions to Help You Choose the Right PaaS for your Enterprise Richard Seroter Senior Product Manager @rseroter
- 16. There can be “right” and “wrong” choices for which PaaS to use in your enterprise. 16 confidential Tier3.com http://www.flickr.com/photos/begnaud/243996426
- 17. Here are nine questions to ask yourself when choosing the right PaaS for a given situation. 17 confidential Tier3.com http://www.flickr.com/photos/ianpoley/2745040048
- 18. #1 - Should your PaaS be public or private? 18 confidential Tier3.com
- 19. #2 – Do you need a PaaS where you build – or assemble – applications? 19 confidential Tier3.com
- 20. #3 – Does the PaaS offer the frameworks and sizing that you need? 20 confidential Tier3.com http://www.flickr.com/photos/thed34n/4787791908
- 21. #4 – How portable are applications targeted at this PaaS? 21 confidential Tier3.com
- 22. #5 – What complimentary application services does the PaaS offer? 22 confidential Tier3.com
- 23. #6 – How does someone interact with the PaaS? 23 confidential Tier3.com
- 24. #7 – Can you extend the PaaS to meet your custom needs? 24 confidential Tier3.com http://www.flickr.com/photos/foshie/508031237
- 25. #8 – What OTHER workloads are in the cloud with the PaaS? 25 confidential Tier3.com
- 26. #9 – What is your main priority? Development speed? Maintenance? Control? Choice? 26 confidential Tier3.com
- 27. Look for the PaaS that meets YOUR needs from both a functional and operational perspective. 27 confidential Tier3.com
- 28. Special Offer • From Cloud Elements – free design assessment – Needs analysis & recommendations • From Tier 3 – a free trial of Web Fabric – Up to 30 days or $1000 of usage, whichever comes first – PaaS based on Cloud Foundry, with support for many popular dev environments, including .NET • We will both be in touch regarding next steps 28 confidential Tier3.com
Notes de l'éditeur
- At Cloud Elements we help companies build SaaS applications faster. We do this by combining three capabilities: (1) A team of experienced SaaS developers; (2) Re-useable integrations to leading cloud services; (3) and leveraging PaaS as the platform we build on.In fact we only build apps at the PaaS tier based on the significant productivity gains that are developers achieved vs. building directly on the IaaS layer.Today we will share some of our experiences in using PaaS services.
- Our focus today will be on building applications that are optimized for the cloud NOT JUST migrated or virtualized.Gartner coined the term “Cloud-Optimized” referring to apps that meet these 5 characteristics.Apps that are multi-tenant, service based and elastic.
- So Let’s start briefly with a definition of what a PaaS is ...PaaS is the most misunderstood layer of the cloud. It’s the “Build It” layer. Your application dev and deployment environment that understands how to behave well in the cloud. To scale efficiently.It’s elastic and service based. It also serves as an abstraction layer between your app and the infrastructure ...much as Linux does on traditional hardware.
- A PaaS typically provides four primary services:Application runtimes such as Java, Ruby, Node, .NetStructured and No-SQL data servicesMessaging & Queing such as RabbitMQAnd Application Management such as monitoring, and alerting, application level resource management and app scaling and deployment services.All of these services will seamlessly scale across your infrastructure saving significant dev effort.Some popular PaaS platforms include Cloud Foundry, which Tier 3 is based on, Heroku, Force.com, Azure, and open shift.
- Prior to founding Cloud Elements our team built 2 large-scale SaaS businesses, Channelinsight and Locationinsight.We built these businesses before PaaS was available and had to essentially develop our own PaaS layer. As our business scaled we spent millions in DevOps costs that could have been avoided with today’s platforms. For example we had to build on our own cloud-aware monitoring and app resource management capabilities with significant cost.As we’ve deployed PaaS we have experienced first-hand the significant cost savings which we have found to be greater than 30%
- Even if you are starting with a Private Cloud deployment ... you can gain these benefits from a PaaS by leveraging the same underlying platform used by public cloud providers such as Tier 3.Open source platforms such as CloudFfoundry and Open Shift are perfect for the enterprise in that they can be deployed in your private cloud and then can be migrated to hybrid and public instances. These open PaaS offering can be deployed to nearly all of the leading infrastructure providers including AWS and Rackspace giving you tremendous options.We’ve also moved clients from private to public clouds in hours vs. weeks when they built on top of IaaS.A PaaS can also help you standardize the set of app and data services to specific versions that your team will use further saving maintenance and support costs
- We believe in architecting applications from the PaaS outward.It is surprising how many companies build to the IaaS and make that selection first vs. letting their choice of PaaS provider drive the choice of IaaS.You can gain significant benefit, particularly in portability, by using the services offered by your PaaS first and making clear architecture decision between the tiers.
- For Example, Use the IaaS for what it is meant to be. Cost effective Networking, computing, and storageMany of the services offered by a PaaS are also offered at the IaaS tier such as data and app services. The problem is that you can become locked in and we’ll discuss an example later.But by leveraging the PaaS services you can be more productive and scalable.However, there are some PaaS options that are monolithic in that they integrate the PaaS and IaaS tiers such as force.com and Azure. These can be good choices if portability and flexibility are not a concern.
- Recently we worked with a retail client who developed their app directly on AWS and built on RDS which is a proprietary version of MySQL. When they decided to move to a private cloud deployment for performance reasons they found that it took weeks to rebuild the data in their new environment.However with another client, a leading physicians network, we deployed using Cloud Foundry and we were able to migrate them from a private to hybrid cloud configuration in less than a day.We regularly set up environments for clients in less than a day vs weeks prior to using Cloud Foundry.
- In summary we believe the productivity gains are significant enough to warrant driving your architecture and design from the PaaS tier vs the IaaS. We believe in the future nearly all cloud apps will be developed from the PaaS outward whether in a private or public cloud.The benefits are that significant.
- There is no perfect PaaS for all cases, but one can make the wrong choice for their given application or needs.
- Public, private, virtual private? Which geographies is this accessed from?Considerations:Who is accessing this PaaS?Where are the users at?Do you have the existing infrastructure to host this internally?How mature is your existing infrastructure operations team?
- How much do you want to build vs. assemble? If you want to assemble a PaaS and quickly get going, you use something like Force.com that has tight restrictions, but a wide set of services that are specific to that platform. If you prefer to build custom apps, then you go with a coding-oriented PaaS like Cloud Foundry.Considerations:Who are the “developers”? Technical staff or business analysts?What type of applications do you need?Excel and Access replacements?Entirely custom applications?
- What languages and frameworks are your apps written in? How inter-connected are they to other assets in your enterprise? How complex are the applications and what type of hardware configuration (CPU/RAM/storage) do you often need?Considerations:Are there dominant programming languages used by your developers?How complex are your custom applications?Resource intensive?Unpredictable usage?Public facing where spikes are possible?
- Do you care if applications can (or can’t) be moved between clouds, or even easily between on-premises sandboxes and the production PaaS?Considerations:Do you use distinct dev/test/prod environments?Do you currently have a mixed environment with some things in the public cloud, and some not?Are you using more than one public cloud?
- IdentityUse existing on-prem providers or common web-based IdPsStorageObject storageDatabaseRelational and NoSQLMessagingQueuing, ESBBillingChargebacksLoggingCentralized frameworkService CatalogCachingShared, app-onlyMonitoring3rd party service curationNew RelicSaaS connectorsFunctional add-ons
- New and existing tools, APIs, integration points, source control system integration, testing (functional/performance)Considerations:Have major investment in operations tools (monitoring, alerts)?Do you build “mash up” operations that leverage APIs to access data in other systems?
- Does the PaaS have hooks for adding custom extensions? Is it open source so that you can fork it for specific purposes? Does it matter? May decrease portability and cost of ownership, but assist in functionality capability.Considerations:Do you have specialized needs because of your industry or unique domain?Do you have a strong engineering team?
- What other corporate assets are deployed to the cloud that is running the PaaS? Principles of data gravity that state that applications and services gravitate to where the data resides. IaaS + PaaS is a powerful combination and a standalone PaaS will rarely run the entire cloud portfolio.Considerations: Are you using an IaaS provider?Do you have SaaS investments?Where is your data?
- What matters most? Speed of development? Maintenance? Control? Freedom? Language choice? Considerations:* Look at existing app dev practices to see what you value. Simplicity? Customization? Mature products? Emerging technology?