Architecting for the Cloud Tamir Dresher Chief Architect

Architecting for the Cloud Tamir Dresher Chief Architect @ Clarizen Twitter: @tamir_dresher

CLARIZEN - ENTERPRISE WORK COLLABORATION FOUNDED IN 2006 ENTERPRISE GRADE Saa. S SOLUTION 99. 95% UPTIME ~2, 000 CUSTOMERS IN 124 COUNTRIES MOBILE APPS & BOTS INTERNAL & EXTERNAL COLLABORATION DEMAND MANAGEMENT PORTFOLIO MANAGEMENT RESOURCE MANAGEMENT PROJECT MANAGEMENT TIME & EXPENSES AUTOMATED WORKFLOW ENGINE FINANCIAL PLANNING INTEGRATIONS APPS MARKETPLACE REPORTS & DASHBOARDS

!SPOF ~SPOF NOT(SPOF) SPOF – SINGLE POINT OF FAILURE

“ Distributed systems are never "up"; they exist in a constant state of partially degraded service. Accept failure, design for resiliency, protect and shrink the critical path. HTTPS: //OPENSOURCE. COM/ARTICLE/17/7/STATE-SYSTEMS-ADMINISTRATION Image by ”

SOLID Principles != OOP Single Responsibility Principle Open Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle

Think services not servers SERVERS ARE DISPOSABLE RESOURCES

Observability YOU CAN’T FIGHT WHAT YOU CAN’T SEE

ry recove ing d r a s alarm rou ting bo on le a sc Automate arch iving

Don’t seek perfect, just Good Enough. KISS KEEP IT SIMPLE STUPID

@tamir_dresher

Use cases 1. A system that collects 15 Billions events per day and process them and a service needs to be triggered if a certain pattern is detected 2. Let’s build Slack 3. Let’s build waze Points to consider Managed vs. Unmanaged Global distribution …