SlideShare a Scribd company logo

Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017

•Download as PPTX, PDF•
•
Codemotion
Codemotion

Service Fabric è la piattaforma, utilizzabile sia su Azure, sia on-prem che su altri cloud provider, per l'implementazione, distribuzione e gestione di soluzioni stateful e scalabili basate su microservizi. La sessione consentirà di capire quali sono i concetti alla base di Service Fabric e quali servizi e funzionalità fornisce la piattaforma sia a livello di infrastruttura che per lo sviluppatore.

Related slideshows

Five Early Challenges Of Building Streaming Fast Data Applications
Five Early Challenges Of Building Streaming Fast Data ApplicationsFive Early Challenges Of Building Streaming Fast Data Applications
Five Early Challenges Of Building Streaming Fast Data Applications
 
The Cloud Native Stack
The Cloud Native StackThe Cloud Native Stack
The Cloud Native Stack
 
Azure saturday Pordenone 2019 - ML.NET model lifecycle with azure devops
Azure saturday Pordenone 2019 - ML.NET model lifecycle with azure devopsAzure saturday Pordenone 2019 - ML.NET model lifecycle with azure devops
Azure saturday Pordenone 2019 - ML.NET model lifecycle with azure devops
 
1 of 20
L'approccio ai microservizi secondo Service Fabric Massimo Bonanni massimo.bonanni@microsoft.com - @massimobonanni CODEMOTION MILAN - SPECIAL EDITION 10 – 11 NOVEMBER 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Traditional application approach Microservices application approach • A microservice application segregates functionality into separate smaller services. • Scales out by deploying each service independently with multiple instances across servers/VMs • A traditional application has most of its functionality within a few processes that are componentized with layers and libraries. • Scales by cloning the app on multiple servers/VMs App 1 App 2App 1
• Single monolithic database • Tiers of specific technologies Data in Traditional approach Data in Microservices approach • Graph of interconnected microservices • State typically scoped to the microservice • Remote Storage for cold data Stateful services Web presentation services Stateless servicesSQL DB or No-SQL Mobile apps Web Tier Services Tier Data Tier Monolithic Databases are shared across services. Stateless services with separate stores Each microservice owns its model/data! SQL […] Database servers are usually the bottleneck Cache Tier Cache doesn’t help much for massive data ingress (Events, IoT, etc.)
Microservices Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healingData Partitioning Automated Rollback Health Monitoring Placement Constraints
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
60bn events/day
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017
Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017

More Related Content

Massimo Bonanni - L'approccio ai microservizi secondo Service Fabric - Codemotion Milan 2017

  • 1. L'approccio ai microservizi secondo Service Fabric Massimo Bonanni massimo.bonanni@microsoft.com - @massimobonanni CODEMOTION MILAN - SPECIAL EDITION 10 – 11 NOVEMBER 2017
  • 4. Traditional application approach Microservices application approach • A microservice application segregates functionality into separate smaller services. • Scales out by deploying each service independently with multiple instances across servers/VMs • A traditional application has most of its functionality within a few processes that are componentized with layers and libraries. • Scales by cloning the app on multiple servers/VMs App 1 App 2App 1
  • 5. • Single monolithic database • Tiers of specific technologies Data in Traditional approach Data in Microservices approach • Graph of interconnected microservices • State typically scoped to the microservice • Remote Storage for cold data Stateful services Web presentation services Stateless servicesSQL DB or No-SQL Mobile apps Web Tier Services Tier Data Tier Monolithic Databases are shared across services. Stateless services with separate stores Each microservice owns its model/data! SQL […] Database servers are usually the bottleneck Cache Tier Cache doesn’t help much for massive data ingress (Events, IoT, etc.)
  • 6. Microservices Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healingData Partitioning Automated Rollback Health Monitoring Placement Constraints

Editor's Notes

  1. 30 secs
  2. 1 min