4. Ingredients:
● Hours of thinking
● Hours of Putting thoughts on paper
● Time making the thoughts communicable
● “The Review Meeting” -- a ceremony
● [Optional] Hours arguing about some points
● Tax: making some changes
● [Optional] Post work (update doc, more meetings)
● => Happiness for doing “the right thing”
http://www.seriouseats.com/
5. ASTMe
A structure that makes sense
DSS
It’s the Database Schema, Stupid
PID / DSS-PID
Polishing implementation details
http://www.seriouseats.com/
18. design.practices
○ Understand the context properly
○ Review Main Decisions (aim: assumptions)
○ Iterate the Model & Flow
○ Activate your own checklist
19. ● Alternative #1:
○ Pros: ….
○ Cons: …
● Alternative #2: SELECTED
○ Pros: ….
○ Cons: …
● Alternative #3:
○ Pros: ….
○ Cons: ...
20. ● Alternative #1: RabbitMQ
○ Pros: simple, efficient,..
○ Cons: how to recover if messages lost?
● Alternative #2: Service polls the source
○ Pros: ability to recover, smaller per-message overhead
○ Cons: new dependency between services
Alternative #2 selected
21. and
Brainstorm Database Schema, but:
Eliminate the f**&!*n types:
“Number”, “text”, “bool” are
enough
Drop technical fields
(“created_at”)
Drop FKs, Nullability etc.
Assure Good Business ⇔ Software Mapping
Walkthrough the code+model - for verification