Viewpoint On Cloud Computing - Collabera

More documents

Recommendations

Info

Value. Accelerated. o Hybrid <strong>Cloud</strong>: enterprises that use a combination of the above two clouds generally fall in the classification of hybrid clouds. Key characteristics that qualify as IaaS offerings includes, o Automated Provisioning o Self-service portal o Ability to monitor resources and application performance Key vendors in this space include Microsoft, Amazon, VMWare, GoGrid, Flexiscale and Terremark among others • Platform as a Service: This is the next level of abstraction where vendors typically abstract the infrastructure and provide frameworks, runtime libraries, tools and IDE to develop/test cloud apps locally and deploy/host these apps in the cloud. Key characteristics that qualify as PaaS offerings includes, o Flexible services platform that provides a framework and a consistent programming model to develop o Internet standards based and interoperable with existing on premise apps/other cloud services o Allows natural extension of existing investments Key vendors in this space include Microsoft Azure, Amazon, Google App Engine and Force among others. • Software as a Service: Also termed Application as a service, includes ready to use applications across CRM, HRM, Financial Management domains and productivity tools like Office and Collaboration (email, messaging, blogs, wikis). Generally licensed on a per-user basis. Key characteristics that qualify as SaaS offerings includes, o Anywhere access and management of software on a pay per user basis o Supports single instance multi-tenant architecture for horizontal scalability o Can integrate/work with existing software investments Key vendors in this space include Microsoft, Zoho, Google Apps, Salesforce CRM, IBM LotusLive among others.
Traditional vs. <strong>Cloud</strong> based approach: A typical business case scenario Prior to cloud computing, business analysts/architects would capture functional/non-functional requirements and accordingly come up with application and deployment architecture that would support these requirements. Over the years, architects have been able to abstract and extract patterns for these commonly needed requirements. Let’s imagine an application that accepts user queries related to income computation and facilitates online filing of Tax returns. For completeness sake, if we were to take functional/non- functional scenarios, we wouldn’t see a major variation in design/architecture of the functional pieces between traditional and the cloud based approach, however it’s the non-functional requirements where one sees the most variation. Let’s take couple of NFRs and do a quick comparison of the solution options, advantage/disadvantage for each of these requirements between the traditional and the cloud based approach: Benefits, Risks & Challenges Business Benefits • Zero capital expenditure, minimal operational expenditure • Just in-time infrastructure availability • Dynamic scaling of resources leading to efficient resource utilization • Pay as you go utility style billing Value. Accelerated.
Page 1 and 2: Position Paper Viewpoint on Cloud C
Page 3: • Platform/Framework as a Service
Page 7 and 8: • IaaS - key vendor comparison ma
Page 9 and 10: Conclusion Every passing day, new v

Viewpoint On Cloud Computing - Collabera

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?