3. .NET Services
SQL Services
Applications
Live Services
Windows Azure
Applications
Windows Windows Windows Others
Server Vista/XP Mobile
4.
5. Logique Métier
…
Ajouter de nouveaux locaux
Ajouter de nouvelles fonctions en « live »
Appliquer les patchs OS Middleware &
Diagnostiquer les défaillances de services
Administration
Ajouter des capacités de stockage
Gérer les augmentations de trafic
Prévoir les défaillances matérielles
Datacenter
6.
7.
8.
9. Dynamics Windows
Google App
Azure
Salesforce
CRM , Azure
Engine, EC2
Services
Gmail
Exchange Fabric
Force
Platform
Online (Raw)
IaaS
PaaS SaaS
Cloud Computing
Utility Computing
Grid Computing
Super
Cluster
Computing
Computing
10.
11.
12.
13. Feature Microsoft Amazon Google VMware
Availability CTP (Alpha) Yes, commercially available In public beta Announced
Computing You provide .NET code for front-end and back- Elastic Compute Cloud (EC2) You write your web Lets you easily move your virtual
Architecture end servers which allows you to upload your XEN application in Python or machines between environments
Microsoft then runs on Windows 2008 virtual virtual Django with a specific and
machines according to your machine images to the set of limitations set by run them on premise or at any
environment specifications (how many machines infrastructure and gives you APIs Google and submit the partner datacenter.
of each kind you need, and so to instantiate and application code to them.
on.) manage them.
Load balancing Yes Yes Yes Not announced
Storage Yes: application storage and SQL services Yes: Simple Storage Service (S3) Yes: database Datastore Not announced
and SimpleDB APIs
Message queuing for Yes: queues in Windows Azure storage Yes: Simple Queue Service No Not announced
machine (SQS)
communcations
Integration with other So called .NET services (aka BizTalk in the No Yes, with existing Google No
services cloud): services: authentication,
Access control services, workflow service, mail, base, calendar,
service bus. contacts, documents,
Live Mesh pictures, spreadsheets,
Various Live services (contacts, mail, maps and YouTube.
so on.)
At the moment, all these components do not
seem to be integrated with
the solution but rather bundled.
Tied to the vendor Yes Yes Yes No, the VMs can be hosted by any
datacenter of the partners or used on-premise
Development tools Yes, integration into Visual Studio, support for Not applicable. Amazon simply Yes, have basic editing, Not applicable. VMware simply
any .NET languages, runs your virtual machines and local simulation, and runs your virtual machines and
does not deployment tools. does not
care which development platform Language selection care which development platform
you are using on top of the base limited to Python and you are using on top of the base
OS. Django. OS
Application-level tools
such as Google Web
Toolkit (GWT) do not
seem
to have any integration
with Google App Engine.
30. .NET Win XBOX
IE8 Office WPF Vista OC Windows Mobile 7
CF Embed 360
IIS 7 SL Streaming WCF
.NET Framework
Ad BTS Adapters
BizTalk 2006 R2
MOSS 2007 .NET Framework 3rd Party MOSS 2007 BDC
Center
Windows WF Windows WF
AD / ADFS ILM
SQL
SQL BizTalk / MOSS 2007 BizTalk Server
IIS 7 Live Services .NET Services .NET Services
Services
Server BizTalk.Net .NET Services .NET Services
Windows Server 2008 WS 2008 HPC Windows Server 2008 Hyper-V
Windows Azure
50. Visual Studio
Projets « templates »
Débogage disponible
Platefome .Net
.Net, IIS7, WCF
« The cloud on your desktop »
Bouchons disponibles ( mode offline )
51.
52.
53.
54.
55.
56.
57. Total compute usage: 2000 VM hours
Cloud storage capacity: 50GB
Total storage bandwidth: 20GB/day
58.
59. Scale-out not scale-up
Add and remove capacity on demand
Pay for what you use as you go
Automation is key to reducing costs
60. Failure of any given node is expected
View each node as a cache
State has to be replicated
No one-time install step
Applications need to reinitialize on restarts
Do not assume previous local state is
available
Configuration changes due
to load or failures
Handle dynamic configuration changes
61. Services are always running
Service rolling upgrades/downgrades
Services must handle data schema changes
Services are built
using multiple nodes/roles
Document service architecture
Document communication paths of elements
Services can grow very large
Careful state management at scale is needed
62. Windows Azure manages services not just
servers
Tell it what you want, and it will automate the
details
System manages services, nodes, and network
Automates service life-cycle management
Model-driven automation
Allocation, deployment, and service-level
management
Turns pool of physical resources
into shared compute fabric
Pay for what you use
Platform insures service isolation
63. Goal is to automate life cycle as much as possible
Maintain
Provisionin Deploymen
Coding and
goal state
g t
Modeling
Desired
New
Mapping and Monitor
configuration
services deploying to React to
and actual events
updates hardware
Network
configuration
Automated
Automated
Developer/
Developer
Deployer
64. Describes service as distributed entities
Authored by service developer
Configured by service deployer
Logical description of the services
Same model used for testing and production
Mapped to actual hardware
at deployment time
Powerful declarative composition
language
Can describe simple to very complex services
65. Public
Internet
Template automatically maps to service model
Frontend
Background
Web
Process Role
Role
Load
Balancer
Fundamental Services
Load Balancer Channel
Endpoint
Interface
Directory Resource
66. Service
Set of roles, groups,
and channels
Role
Program, execution entity
Group
Set of other groups,
roles and channels
Endpoint
Communication end
point exported by role
Channel
Logical load-balancers
and switches
Interface
Exposed by services
Configuration settings
Developer settings
System settings
70. Windows Azure PDC release
Automated service deployment from bare metal
Subset of service model –
simple set of service templates
Support for changing number of running instances
Simple service upgrades/downgrades
Automated service failure discovery and recovery
Automated hardware management
Include automated network load-balancer management
In calendar year 2009
Expose more of underlying service model
Richer service life-cycle management
71. Windows Azure PDC release
Managed code/ASP.net
Running in fixed-sized VM instances
External virtual IP address per service
Service network isolation enforcement
In calendar year 2009
Native code support
Richer network support
Also, in 2009 will be in multiple
data centers
72. Cloud services have specific design
considerations
Always on, distributed state,
large scale, and failure handling
Windows Azure is an
operating system for the cloud
Scale out, dynamic, and on-demand
Windows Azure manages services not just
servers
Tell it what you want, and it
will help automate the details
Windows Azure frees developers
from many platform issues
Allows developers to concentrate on
application logic instead of platform issues
73.
74. Extend existing Deploy Complete Compose New Application
On-Premise Application Application in the Cloud from Cloud Services
79
78. • Parallel and distributed processing
• Image processing and rendering
• Media content transcoding and publishing
• Share-able reference data
• Search indexes, Catalogs
• Maps, profiles, blogs, files, documents, etc.
• Composite services, mashups
• Multi-enterprise business applications (MEBA)
• Inter-organizational (B2B) business processes
• Extend enterprise SOA to other enterprises
79.
80. Learn Build Extend
Download the SDK’s & build
Find out more at Provide feedback on
www.azure.com your service/application technology & model
Use MSDN resources Provision & deploy your Participate in blogs &
msdn.microsoft.com/en- service on Azure forums
us/azure
Participate in readiness
activities
83. Les applications distribuées sont très différentes
des applications centralisées ou client/serveur !
Hypothèses fausses sur le réseau !!!
1 – Le réseau est fiable. 5 – La topologie ne change pas.
2 – La latence est nulle. 6 – Il y a un administrateur.
3 – La bande passante est infinie. 7 – Le transport ne coûte rien.
4 – Le réseau est sécurisé. 8 – Le réseau est homogène.
• Le réseau n’est simplement pas un composant
– Le réseau introduit de la latence
– Le réseau est “partitionné” par la latence
3 4
1 2
Latence
84. • Le théorème CAP (Consistency, Availability, Partition)
– “There are three properties that are commonly desired: consistency,
availability, and partition tolerance. It is impossible to achieve all
three at the same time.
• Consistency + Availability
A
C
• Single site / Cluster database
P • Two phases commit
• Consistency + Partition
A
C • Distributed database / Distributed looking
• Pessimistic looking
P
• Availability + Partition
A
C • Distributed cache/ DNS
P • Optimistic looking
85. Contexte des applications
Fondamentalement Partitionnées (latence)
latence réseau => Partition du SI
Restent Consistance et Disponibilité
Objectifs des applications ?
Hautement Disponibles
=> recherche de Disponibilité
Donc Consistance doit être relaxée
réplication (systèmes de fichiers, SGBDs)
