Upload
alexander-samarin
View
184
Download
0
Embed Size (px)
Citation preview
Architecting of modern information systems
Module 6Modern disruptive technologies
A. Samarin
Architecting modern information systems - Module 6 2
• Cloud computing • Social computing • Free and Open Source Software; Open standards
© A. Samarin 2012
Topics
Architecting modern information systems - Module 6 3
• Cloud Computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction [NIST]
© A. Samarin 2012
Definition
Architecting modern information systems - Module 6 4
• Private cloud: The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.
• Community cloud: The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.
© A. Samarin 2012
Deployment models (1)
Architecting modern information systems - Module 6 5
• Public cloud: The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
• Hybrid cloud: The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).
© A. Samarin 2012
Deployment models (2)
Architecting modern information systems - Module 6 6
Type Definition Type of Services offered
Examples
SaaS Software as a Service – typically deliv ers software applications as services (SaaS) through the browser to thou sands of customers using a scalable multi-tenant architecture
Business AppsOffice productivity CollaborationSecurity
Salesforce.comWebex (Cisco)Symantec.Cloud
IaaS Infrastructure as a service - delivers computer infrastructure - storage and virtual servers that IT can access on demand. clients buy those resources as a fully outsourced service rather than purchasing them in-house.
ComputingStorage
Amazon web ser vicesVerizon CaaS
PaaS Platform as a service - relates to the offering of a development and deploy ment environment as opposed to a packaged application. Intended for use by a company looking to develop a custom application.
Development application components and environ ment
Microsoft AzureGoogle Apps
© A. Samarin 2012
Service models (2)
Architecting modern information systems - Module 6 7© A. Samarin 2012
Service models (1)
Architecting modern information systems - Module 6 8© A. Samarin 2012
Promises from vendors
Architecting modern information systems - Module 6 9
• Cost containment• Business continuity • Procurement• Flexibility of resources provisioning• Easy access to advanced skills set• The Economic Benefit of Cloud Computing:
– Lower Costs– Cap-Ex Free Computing– Deploy Projects Faster, Foster Innovation – Scale as Needed – Lower Maintenance Costs – Resiliency and Redundancy
© A. Samarin 2012
Cloud drivers
Architecting modern information systems - Module 6 10
Our cloud strategy
• Architect our way to clouds• Agree on a decision matrix – what application / tool can go
into which type of cloud• Working together • Evaluate the cloud option in all new IT projects (“cloud
first” approach)• Making services more cloudable
© A. Samarin 2012
Architecting modern information systems - Module 6 11
• GOLD - classic within enterprise computing• ORANGE - within enterprise private cloud• GREEN - outside enterprise and enterprise-managed
private cloud• BLUE - outside enterprise and service-provider-managed
private cloud• VIOLET - cloud (outside enterprise and service-provider-
managed by definition)
© A. Samarin 2012
Deployment zones
Architecting modern information systems - Module 6 12
Different deployment ZONEs
© A. Samarin 2012
HQ
VIOLET
GREENBLUE
YELLOW
GOLD
BO
Architecting modern information systems - Module 6 13
Scenario 1 – now
© A. Samarin 2012
HQ
BO
Architecting modern information systems - Module 6 14
Scenario 2 – partial private cloud
© A. Samarin 2012
HQ
BO
off-premises and service-provider-managed private cloud
off-premises and enterprise-managed private cloud
Architecting modern information systems - Module 6 15
Scenario 3 – externalised private cloud
© A. Samarin 2012
HQ
BO
off-premises and service-provider-managed private cloud
BC
Architecting modern information systems - Module 6 16
Scenario 4 – no satellite
© A. Samarin 2012
HQ
BO
off-premises and service-provider-managed private cloud
BC
Architecting modern information systems - Module 6 17
• A systematic procedure for evaluation of cloudability of an IT service – what ZONEs are acceptable for a particular IT service
• The evaluation consists of two parts– ranking of an IT service by several characteristics, and– decision table for acceptability of cloud solutions
• Making IT services more cloudable– virtualisation– internal unification– use of industry de-facto standards– real services à la SOA– assembling of services by processes (BPM)
© A. Samarin 2012
Cloud-first approach
Architecting modern information systems - Module 6 18© A. Samarin 2012
Profiling services
Architecting modern information systems - Module 6 19© A. Samarin 2012
Profiling services - example
Architecting modern information systems - Module 6 20© A. Samarin 2012
Decision taking
Architecting modern information systems - Module 6 21© A. Samarin 2012
Decision taking - example
Architecting modern information systems - Module 6 22
• Rules for the recommendation row:1. If at least one “NO” then “NO”2. If no “OK” and some “maybe” and “IaaS/PaaS/SaaS” then “maybe”
+ “IaaS/PaaS/SaaS”3. If some “OK” and no “maybe” and “IaaS/PaaS/SaaS” then “OK” +
“IaaS/PaaS/SaaS”• CAPEX and OPEX are functions of a service and a zone type.• Resume: 3 zones are not recommended, 2 accepted as SaaS• 1st preference SaaS in BLUE zone (CapEx, OpEx, leadtime)• 2nd preference SaaS in GREEN zone (CapEx, OpEx, leadtime)
© A. Samarin 2012
Recommendation - example
Architecting modern information systems - Module 6 23
Immediate candidates for private cloud
• E-mail• E-mail archiving• Document management• Document archiving• End-points backup
© A. Samarin 2012
Architecting modern information systems - Module 6 24
• Cloud computing • Social computing • Free and Open Source Software; Open standards
© A. Samarin 2012
Topics
Architecting modern information systems - Module 6 25
• Social computing an area of computer science that is concerned with the intersection of social behavior and computational systems
• Creating social conventions and social contexts through the use of software and technology. Thus, blogs, email, instant messaging, social network services, wikis, social bookmarking, etc.
• Supporting “computations” that are carried out by groups of people. Examples: collaborative filtering, online auctions, prediction markets, reputation systems, computational social choice, tagging, and verification games.
© A. Samarin 2012
Social computing
Architecting modern information systems - Module 6 26
• Political domain– E-consultation as an umbrella for different means of expressing
the voice of the people (similar to direct democracy): e-polls, e-voting, etc.
– Transparency of the legislative powers (e.g. parliament, deputies, decisions)
– Easy access to the legal knowledge base – Voting rights (different levels, as well as expatriates)
• Social computing can support e-consultations
© A. Samarin 2012
In the context of e-gov
Architecting modern information systems - Module 6 27
• Constitute interactive “tell-us-what-you-think” on-line services where ordinary citizens, civic actors, experts, and politicians purposively assemble to provide input, deliberate, inform, and influence policy and decision making.
• Usual challenges:– population coverage– integrity– visibility– transparency and disclosure obligations are vital– usual distrust towards new electronic applications– balance of central and local power
© A. Samarin 2012
E-consultations
Architecting modern information systems - Module 6 28
• Only authorized person can actively contribute (i.e. add some text) in e-consultation services.
• The identity of the person may is hidden.• The enrollment will include the identity verification. • Further a person can hide his/her identity under an avatar. • The correspondence between an avatar and the identity is
secret, but may be disclosed in case of misbehavior. Example: Facebook.
© A. Samarin 2012
Privacy considerations
Architecting modern information systems - Module 6 29© A. Samarin 2012
Question and answer discussion forums
Architecting modern information systems - Module 6 30© A. Samarin 2012
On-line polls
Architecting modern information systems - Module 6 31
• A person (or an association) initiates a formal demand to public services. Such a demand should start a process which should lead to a meaningful response. People, other than the initiator, can express their opinion (support or not) about the demand.
© A. Samarin 2012
E-petitions or on-line testimonies
Architecting modern information systems - Module 6 32
• A time-bounded nominee-only group open discussion on issues of public interest.
© A. Samarin 2012
E-panels
Architecting modern information systems - Module 6 33© A. Samarin 2012
Editorial consultations
Architecting modern information systems - Module 6 34© A. Samarin 2012
E-voting (1)
Architecting modern information systems - Module 6 35© A. Samarin 2012
E-voting (2)
Architecting modern information systems - Module 6 36© A. Samarin 2012
E-voting (3)
Government
Internal existing
application
Coordination and integration
e-Government
© A. Samarin 2012 Architecting modern information systems - Module 6 37
Reference e-government architecture
Collaborative extranet between partners and government
Internal existing
application
Internal existing
application
Partners (citizes, businesses, etc.)
© A. Samarin 2012 Architecting modern information systems - Module 6 38
Platform pattern
e-GovernmentCollaborative extranet
A1 A2 ……… An
Platform
Coordination and integration
Partners (citizes, businesses, etc.)
Government
© A. Samarin 2012 Architecting modern information systems - Module 6 39
Common services
e-Government
Authentification
Indetification
Authoritation
Delegation
Content management
Classification
Search
Data
Events
ReportsCoodination
Following-upTraceability
Notification
Processes
Rules
Roles
© A. Samarin 2012 Architecting modern information systems - Module 6 40
Applications and common services
e-Government
Authentification
Indetification
Authoritation
Delegation
Content management
Classification
Search
Data
Events
ReportsCoodination
Following-upTraceability
Notification
Processes
Rules
Roles
APP1 APP2 …… APPn
Architecting modern information systems - Module 6 41
• Imaging an e-voting application – how different political parties can be sure that no tempering of data?
© A. Samarin 2012
Homework 6-1
Architecting modern information systems - Module 6 42
• Cloud computing • Social computing • Free and Open Source Software; Open standards
© A. Samarin 2012
Topics
Architecting modern information systems - Module 6 43
• FOSS is software that is both free software and open source.
• Free refers to the freedom to copy and re-use the software, rather than to the price of the software. "think of free as in free speech, not as in free beer“
• Open-source software is software whose source code is published and made available to the public, enabling anyone to copy, modify and redistribute the source code without paying royalties or fees
© A. Samarin 2012
Terminology
Architecting modern information systems - Module 6 44© A. Samarin 2012
How does it work?
Architecting modern information systems - Module 6 45© A. Samarin 2012
Pros & Cons
Architecting modern information systems - Module 6 46© A. Samarin 2012
To validate
Architecting modern information systems - Module 6 47
• Partnership between private and public parties– Government– Businesses for supporting of FOSS products– Fair game
• Multiple replaceable sources • Extra quality checks for FOSS• Architecture for mixing FOSS and commercial products
– Open standards (data formats and protocols)– SOA– BPM
• Rule-based selection of products© A. Samarin 2012
Ecosystem for FOSS
Architecting modern information systems - Module 6 48
• Publicly available• Developed in an open process by non-profit organisation• Patent-fee free• Examples:
– HTML– XML
• Usually used for– Exchange protocols (opening market for service providers)– Data formats (preserving your assets)
© A. Samarin 2012
Open standards
Architecting modern information systems - Module 6 49
• What FOSS and open standards do you use?
© A. Samarin 2012
Homework 6-2