1 / 11

Architecting for the Cloud

Discover how to design cloud systems that thrive with resiliency strategies, solid principles, and SPOF avoidance. Learn from Chief Architect Tamir Dresher at Clarizen.

chantelr
Download Presentation

Architecting for the Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. !SPOF~SPOFNOT(SPOF) SPOF – Single point of failure

  4. 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 : opensource.com

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

  6. Think services not servers Servers are disposable resources

  7. Observability You can’t fight what you can’t see

  8. recovery routing alarms onboarding Automate archiving scale

  9. Don’t seek perfect, just Good Enough. KISS Keep it simple stupid

  10. @tamir_dresher

  11. Use cases • 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 • Let’s build Slack • Let’s build waze Points to consider • Managed vs. Unmanaged • Global distribution • …

More Related