Cloud Architecting Insights and Best Practices
"Explore key concepts and strategies for architecting in the cloud presented by Tamir Dresher, Chief Architect at Clarizen. Learn about enterprise work collaboration, resilience design, SOLID principles, server management, observability, automation, and simplification. Discover how to handle distributed systems effectively and the importance of embracing failure for building robust cloud solutions."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Architecting for the Cloud Tamir Dresher Chief Architect @ Clarizen Twitter: @tamir_dresher
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 A P P S M A R K E T P L A C E I N T E G R AT I O N S I N T E R N A L & E X T E R N A L C O L L A B O R A T I O N DEMAND MANAGEMENT PORTFOLIO MANAGEMENT RESOURCE MANAGEMENT PROJECT MANAGEMENT TIME & EXPENSES FINANCIAL PLANNING A U TO M AT E D W O R K F L O W E N G I N E
!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 : opensource.com
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
Dont seek perfect, just Good Enough. KISS KEEP IT SIMPLE STUPID
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 1. 2. 3. Points to consider Managed vs. Unmanaged Global distribution
