good podcast:
A Conversation with Amazon CTO Werner Vogels - Software Engineering Daily
"Werner Vogels is the Chief Technology Officer at Amazon, where he has played a pivotal role in shaping the company’s technology vision for over two decades. Before joining Amazon in 2004, Werner was a research scientist at Cornell University where he focused on distributed systems and scalability, both of which are concepts that would later influence the design of AWS. He holds a PhD in computer science and has authored numerous academic papers on the reliability and performance of large-scale systems.He is known for his pragmatic, customer-focused approach to technology and for championing ideas such as “you build it, you run it,” “APIs are forever,” and more recently, Frugal Architecting, which emphasizes cost-effective and sustainable software design."
I. Make Cost a Non-functional Requirement
II. Systems that Last Align Cost to Business
III.Architecting is a Series of Trade-offs
PHASE: MEASURE
IV. Unobserved Systems Lead to Unknown Costs
Cost Aware Architectures Implement Cost Controls
PHASE: OBSERVE
VI. Cost Optimization is Incremental
VII. Unchallenged Success Leads to Assumptions
Werner Vogels' 6 Rules for Good API Design - The New Stack
VI. Cost Optimization is Incremental
VII. Unchallenged Success Leads to Assumptions
Werner Vogels' 6 Rules for Good API Design - The New Stack
- APIs are Forever: Once an API is created, it should never be deleted, or changed
- Never Break Backward Compatibility: Backward capability is a must.
- Work Backwards from Customer Use Cases: come up with a minimal and simplest form of API that you can actually offer,
- Create APIs That are Self Describing and Have a Clear, Specific Purpose
- Create APIs with Explicit and Well-Documented Failure Modes
- Avoid Leaking Implementation Details at All Costs
No comments:
Post a Comment