UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
Cloud Computing 101
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
Hinweis der Redaktion
Agenda for today
A very quick introduction to what cloud computing actually is…
A very quick introduction to what cloud computing actually is…
Some common themes of cloud computing
Another visual explanation
Cloud computing paradigm of computing in which dynamically scalable and often virtualized resources are provided as a service over the InternetUsers need not have knowledge of, expertise in, or control over the technology infrastructure in the "cloud" that supports themThe concept generally incorporates combinations of the following:infrastructure as a service (IaaS)platform as a service (PaaS)software as a service (SaaS)The term cloud is used as a metaphor for the Internet, based on how the Internet is depicted in computer network diagrams and is an abstraction for the complex infrastructure it conceals.
Salesforce.com is held up as the classic example of SaaS – sign up and you have a full featured CRM available to you immediately. Configuration and customisation can all be done via your web browser. “Great – it fits in the SaaS box” you say…but not quite…Force.com is the platform under-pinning Salesforce.com – and on Force.com you can build any type of application you like – CRM related or not. Often implementers will customise salesforce using the force.com platform thereby creating, in effect a hybrid SaaS/PaaS offeringGoogle AppEngine and Windows Azure are essentially straight PaaS solutions – take your application component and deploy into the platform. Azure pushes into the IaaS aspects of cloud computing – for example, by offering relatively low level SQL Server features in a way not dissimilar to what you essentially get when starting an “off the shelf” Windows SQL Server AMI on Amazon EC2.Amazon EC2 is predominantly IaaS; and apart from some specific limitations, mainly around networking, is not too dissimilar from that of mass-market virtualisation providers or what large enterprise IT teams offer their internal customers in “private clouds”.
With AWS a new server can be up and running in three minutes (it used to take Eli Lilly seven and a half weeks to deploy a server internally) and a 64-node Linux cluster can be online in five minutes (compared with three months internally).
develop, test, deploy, host and maintain applicationssource code control, version control, dynamic (interactive) multiple user testing, roll out and roll back with the ability to audit and track who made what changes when to accomplish what purposeWeb based user interface creation toolsWYSIWYG etc etcMulti-tenant architectureIntegration with web services and databasesSupport for SOAP and REST interfaces allow PaaS offerings to create compositions of multiple Web services, sometimes called "Mashups".Support for development team collaborationThe ability to form and share code with ad-hoc or pre-defined or distributed teams greatly enhances the productivity of PaaS offerings. Schedules, objectives, teams, action items, owners of different areas of responsibilities, roles (designers, developers, tester, QC) can be defined, updated and tracked based on access rights.Utility-grade instrumentation
Resources delivered as a service including servers, network equipment, memory, CPU, disk space, data center facilities,Dynamic scaling of infrastructure which scales up and down based on application resource needs AMAZON 50k per dayVariable cost service using fixed prices per resource componentMultiple tenants typically coexist on the same infrastructure resourcesEnterprise grade infrastructure allows mid-size companies to benefit from the aggregate compute resource pools
No huge capital investment required so less risky financiallyMinimises time to value period – 30 day free trial shows quick benefitsEncourages consistent utilisation and therefore reduces roll out headachesSaaS reduces IT depts requirements to spend time sysadmining – therefore can do higher value strategic IT stuff
- The data from the 3rd party is normally available via a web application which is human accessible only.- In order for anyone to see the data, they need to log in and then drill down to the level they require.- The layout of the web application is somewhat convoluted and not suitable for executive level.- The data is made suitable for display in executive summary by automating the data access via the 3rd party API
Need to assess how change will effect existing IT assetsAssess data security needs and ensure external SaaS provider can meet organisation’s requirementsGiven that SaaS has traditionally been seen as a SME delivery methodology – SaaS providers may not have service level agreements already in place – need to ensure SLAs are in place, guarantees are sufficient to meet organisational needs and mitigation provisions are sufficient to cope with a “worst case” situationEnsure prospective SaaS provider has data-migration functionalities in the event that later migration from the SaaS product is required. Ensure access to raw data and contractual agreed access to organisational dataObvious need to ensure that SaaS product will integrate with other organisationally used applicationsIn these post enron days and with sarbanes-oxley requirements SAS70 (Statement on auditing standards #70) is a major issue. Need to ensure SaaS provider can provide a SAS70 report and that it meets organisational requirements in terms of privacy and data securityIT departments embracing an open outsourcing or SaaS perspective need to see themselves not as IT gatekeepers but internal consultants offering advice, deployment services and mission critical IT functionality. It moves IT from a technology-centric approach to a service-centric one where it can add value to the organisation within which it operates