What is a modern application Ulrich Uli Homann


















![Failure mode example public int Get. Business. Data(string[] parameters) { try { var config Failure mode example public int Get. Business. Data(string[] parameters) { try { var config](https://slidetodoc.com/presentation_image_h2/93f1905984a7a86f7e0d9e2d3d6b0778/image-19.jpg)

















- Slides: 36
What is a “modern” application? Ulrich (Uli) Homann Chief Architect, Microsoft Services Microsoft Corporation
Each Application The Outcome
CDN caching compute messaging storage database VMs networking business analytics identity commerce automated managed resources elastic usage based Global Physical Infrastructure servers/network/datacenters North Central US, S. Central US, N. Europe, W. Europe, E. Asia, S. E. Asia + 24 Edge CDN Locations
EDW Regulatory Monitoring OA&M OLTP TX SLA Monitoring VAR 0 micro- milli- second minute hour day week month
2. Service call 1. Schedule service 3. Dynamic dispatch 6. Notification Happy customers 4. GPS Telemetry 5. Notification Fleet scheduling Event processing Alert Generation Analysis: Near real-time + historic processing
intelligent network load balancer network activation stateless web and/or application servers stateless “worker” process servers async activation state: queues, database, object store, files…
Monitoring counters Trigger growth at 80% RPS – Initial 99, Growth 80 Content db size – Initial 0. 8 TB, growth 0. 7 TB
Security Managed operations Physical access Designed Redbooks Process Error Messages Defined processes
Data Center Cloud Fabric Application Services Your Services Platform Services 3 rd Party Services
18
Failure mode example public int Get. Business. Data(string[] parameters) { try { var config = Config. Open(_config. Path); var conn = Connect. To. DB(config. Connect. String); var data = conn. Get. Data(_sproc, parameters); return data; } catch (Exception e) { Write. Event. Log. Event(100, E_Exception. In. Dal); throw; } } 19
20
Fault Domains Upgrade Domains • VM rolling upgrades, no availability impact • Failed component can’t take down service • Logical grouping of role instances • Isolated infrastructure • Physical hosts, racks • Network equipment • Two by default • Role instances across 2+ fault domains • Five by default • Role instances spread over upgrade domains • Deployment upgraded for all or one at a time
http: //www. go-gulf. com/blog/60 -seconds
Generation <<ME>> Social group behavior Right information at the right time User preferences User behavior User intent
Learning Connect. Share. Discuss. Microsoft Certification & Training Resources http: //europe. msteched. com www. microsoft. com/learning Tech. Net Resources for IT Professionals Resources for Developers http: //microsoft. com/technet http: //microsoft. com/msdn
Evaluations Submit your evals online http: //europe. msteched. com/sessions




































