Course/Udi-Dahan

(free src: https://learn.particular.net/courses/take/SOA/lessons/1517272-it-ops-service ) Course_ Advanced Distributed System Design - Udi Dahan ToC SOA tenets Service example _) Q&A (no notes, not in free src) Services modelling: Workflows, boundaries and business capabilities UI composition and Branding service IT/Ops service related: Service Boundaries, SOA vs DDD - DDDEU2021 Session_ Service Boundaries - Tjen Wellens 1) SOA Tenets Microsoft original “tenets of SO” 1. autonomous 2. explicit boundaries 3. share contract & schema not class or type (or anything, or db) 4....

(src: Course_ ADSD - Fallacies of Distributed Computing) role: Business Analist role: Architect role: Project Manager Estimates Given a - well-formed team (worked together) - with required skills (has done such things before) - of size S I like how estimates formulated this way, drive Proof-of-Concepts with the sole focus of getting better estimates. This then lowers risk & variability by shifting that to the beginning of the project....

Search for ’natural folding lines’ in the domain Try to find the “natural folding lines” between areas in the domain. how: ask domain experts: “Can you imagine that changing data x ever impact data y” eg. “[hospital] Would the patient changing family name impact which doctor they get treated by” eg. “[webshop] Would changing the description of a product cause the price to change?” When the domain expert looks at you like - "You don't get it at all do you?...

Course_ Advanced Distributed System Design - Udi Dahan Coupling incoming vs outgoing coupling def: incoming coupling def: outgoing coupling clarity: incoming vs outgoing count coupling X->Y x outboing 1 y incoming 1 A->B x outgoing 5 “is this class single responsibility principle” y incoming 1 “how many classes do I have to change” static analysis tool hidden coupling 3 aspects of coupling ...

Course_ Advanced Distributed System Design - Udi Dahan def: Application def: System application !-> connectivity 8 fallacies of distributed computing latency table backward compatibility is a requirement for CD unless you have multiple versions & backward compatibility, dont do CD CD will become Cdowntime functionally separate vs physically separate you can deploy monolith what is logically decoupled Product vs Project maintenance is a bad metaphor, project is better...

Course: Advanced Distributed System Design - Udi Dahan https://learn.particular.net/courses/adsd-online Important info about the course Welcome to the course Distributed System Design- Slides Fallacies of Distributed Computing Introduction: Systems vs. Applications Fallacy #1: The network is reliable Fallacy #2: Latency isn’t a problem Fallacy #3: Bandwidth isn’t a problem Fallacy #4: The network is secure Fallacy #5: The network topology won’t change Fallacy #6: The admin will know what to do Fallacy #7: Transport cost isn’t a problem Fallacy #8: The network is homogeneous Summary: 8 fallacies of distributed computing Fallacy #9: The system is atomic Fallacy #10 : The system is finished Fallacy #10: Towards a better development process Fallacy #11 : The business logic can and should be centralized [[course-adsd-coupling....