• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Best Practices for Building Successful Cloud Projects

Best Practices for Building Successful Cloud Projects






Total Views
Views on SlideShare
Embed Views



5 Embeds 100

http://www.gigaspaces.com 81
http://www.linkedin.com 10
http://www.slideshare.net 5 2
https://www.linkedin.com 2



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Key Points:Focus on discussing the business aspects of Cloud Computing- What business issues are companies trying to solve with cloud computing?What value did moving to the cloud provide these companies?What concerns did these companies need to over come?
  • I came across this graphic a few months ago and thought it was applicable to undertaking a Cloud Projects and relating it to navigating through a mazeJust like any puzzle, there are multiple places to start, more than one path to success, pitfalls and dead ends along the way that you need to avoid.Making the wrong decision can at best case lead to lost time and at worse case lead to high costs and a failed projectAs you may have noticed…There is a lot of hype and buzz around cloud computingIt is cool to be cloud and every vendor now has “Cloud Ware”Remember when it was cool to be SOA? Well it’s not cool anymore Marketing teams around the globe are having a lot of fun coining new terms every dayAnd you need “Urban Dictionary” just to keep up with some of the latest meaningsI hope today to remove some of that confusion for you and help you navigate through the Cloud maze by providing you some real world experiences in what some of the customers that GigaSpaces is working with are thinking and doing with Cloud Computing.
  • I am not going to spend a lot of time on this slide but would like to level set on the terms that I will use today
  • First group is those projects that are looking for an “Enterprise Grade” IaaS/PaaS
  • The Perceived Risks of Newness of the Cloud Computing ModelWhile some kinds of software-as-a-service (SaaS)-style applications are well-established in mainstream use, use of APaaS is new. Therefore, most users are cautious, evaluating the viability of APaaS, especially considering that the leading software vendors have not yet endorsed this model of cloud computing.Proprietary Programming Models and Lack of StandardsThe model-based programming environments of most APaaS are nonstandard (and no standard for such programming presently exists). Other APaaS offerings that are attempting to use established programming languages and programming models for customizable multitenant computing are forced to reduce and alter the standard environments, losing the standard in the process. Thus, the current APaaS offerings lead to exclusive vendor lock-in, a serious barrier for mainstream adoption. A transition from the now-established programming models to the next generation of model-driven style of programming will require a strategic endorsement and backing from the leading software vendors.Data Security ConcernsUse of public cloud computing, whatever model is considered, for mainstream business applications is being delayed. This is because many organizations are concerned about the safety and security of their data. Thus, only the least-sensitive business applications are considered for cloud deployment. CRM is the most popular SaaS application category, and is less data-sensitive than other categories, because it does not address financial transactions. Some ERP and banking cloud applications are emerging, but have not yet reached the mainstream levels of adoption.Maturity of the Leading Software VendorsThe software industry giants have stayed away from the shared-everything, cloud multitenancy model. Instead, they are investing in the shared-hardware model, where elasticity occurs at the level of dynamically allocated virtual machines, while the platform stack above the virtual machine is the standard application server environment. Established software vendors and their users favor this approach, because it preserves their established business applications, tools and skills. Microsoft and other vendors likely will optimize the elasticity of the shared-hardware model to be competitive and, thus, will delay the emergence of a mainstream genuine shared-everything APaaS. However, pressured by the requirements of the SaaS market, the giants will be invested in delivering a genuine multitenant metadata-driven APaaS environment by 2012.Maturing of APaaS: Ready for Enterprise Computing Requirements?To be considered for enterprise-class systems, cloud application platforms must deliver reliable advanced levels of availability, manageability, security, data integrity, service-level agreement guarantees and functional completeness, including application integration, business process management, multichannel user experience, event processing, business intelligence, service-oriented architecture governance and other
  • This is truly a success story on how the economics of Cloud Computing enabled a companies business modelInitial problems occurred when Primatics started to develop their own platform by cobbling together various components:Unreliable, unstable and ended up causing system crashesEach crash required the risk analysis model to have to be restarted from the beginning causing them:Higher costs for re-use of cloud compute resourcesCustomer satisfaction due to missed SLA’sPrimatics learned that development practices that work in a static environment often break in a distributed cloud environment
  • Business drivers;Reduce the cost of delivery of their offering Expand their offering into un-tapped market segments that a large on-premise solution was too costly forWithout a large upfront investment they wanted to prove the market viability and the performance of a SaaS delivered call center application
  • AAR, a leading system integrator specializing in mission critical development projects, has delivered several turn-key solutions on top of GigaSpaces PaaS. GigaSpaces PaaS gives AAR a competitive edge, because it provides their customers the ability to launch new applications in a matter of weeks as opposed to months and at a fraction of the setup costs (development environment, testing environment, staging environment) and hardware costs of traditional projects. GigaSpaces PaaS allows integrators and solution providers to offer turn-key solutions on the cloud with unprecedented robustness, resilience, high availability and performance. Customers want cloud-based projects because they offer faster time to market, more flexibility and better scalability. Integrators benefit from dramatically reducing the total cost of projects, particularly the hardware and setup components, which can translate into improved profit margins or more competitive prices. In addition, integrators can generate ongoing revenues by offering to maintain the project on the cloud – GigaSpaces PaaS can even bill the customer automatically for these services using Amazon’s DevPay system.
  • Use less machine hours – with XAP you can reach 5-10 times the performance of standard implementations. This means you can deliver the same performance with less hardware. On the cloud, this translates into an immediate cost saving – by using less resources, you can save as much as 80-90% of the machine hours required per month.Use less bandwidth and storage – XAP uses its In-Memory Data Grid to keep your data in-memory, ensuring resiliency and consistency, which saves the need to purchase disk-based storage from the cloud vendor. XAP also runs your business logic collocated with your data, reducing the network bandwidth you’ll need to pay for.Run apps only when actually needed – XAP provides complete application lifecycle management, including automated deployment and cleanup (shutdown) of all application instances and middleware (load balancer, web container, database). This enables you to run applications and middleware only as long as it is actually needed. This results in substantial savings of machine hours on the cloud, especially in demo, testing and prototyping scenarios.No need to use the cloud for ongoing development – XAP lets you develop locally using an identical environment to the one running on the cloud. This means that ordinary development and testing does not require purchasing cloud machine hours.No need for additional cloud products such as Amazon’s map/reduce, parallel processing, automatic scaling and monitoring, SQS, SimpleDB, and loadbalancer, because XAP provides all these service out-of-the-box, included in its basic price.Test on the cloud and save in-house testing servers – XAP provides an identical environment for your applications both on and off the cloud, allowing you to test reliably on the cloud and then deploy applications in your local data center. Moving your testing environment to the cloud allows you to eliminate or re-purpose servers dedicated to testing, often more than 1/3 of the servers in a data center.Eliminate platform development costs – with most cloud solutions available today, you will need to develop some middleware/platform capabilities needed by enterprise applications. This is not only time-consuming and risky, but also requires special distributed computing skills. XAP saves you the time and trouble of building platform features yourself, by providing a comprehensive enterprise solution.

Best Practices for Building Successful Cloud Projects Best Practices for Building Successful Cloud Projects Presentation Transcript