1. IMPERFECT
ARCHITECTURE

2. BEN MARX
ARCHITECT
@BGMARX
HIRING!

3. COMPLETE SYSTEM FAILURE

4. API GATEWAY

5. MOST OF THE TIME

6. THIS ONE TIME

7. GATEWAY DISASTERRESPONSE TIMES
NUMBER OF 500S

8. EXPERIENCING THE ARCHITECTURE OF
THE INCOMPLETE, IMPERFECT,
AND IMPERMANENT
HTTP://BIT.LY/2CGRJSL

9. “IN 16TH CENTURY JAPAN, WE FIND AN ARTIST (SEN NO RIKYU) WHO RELIED ON THE
PROPERTIES OF THE IMPERFECT, WHICH IN JAPANESE ARE CALLED WABI, IN ORDER
TO CREATE PHYSICAL OBJECTS THAT INDUCED PARTICIPATORY INTERPRETATION IN
THE VIEWER”

10. 侘寂
WABI-SABI

11. 侘寂
WABI-SABI

12. PEOPLE
SYSTEMS
ARCHITECTURAL COMPONENTS

13. 構成 SYSTEMS

14. CODE DEPLOY
SYSTEM LIFECYCLE
QAPLAN

15. INTRODUCE EVALUATE
ADJUST
SYSTEM LIFECYCLE

16. API GATEWAY REVISITED

17. COUPLED SERVICE DEPENDENCIES

18. APP FALLBACK LOGIC

19. TASK.AWAIT TO TASK.YIELD
external_request = Task.await(task_to_await)
external_request =
case Task.yield(task_to_await, 500) do
{:ok, result} -> result
nil -> :error
end

20. YIELD INSTEAD OF AWAIT

21. GATEWAY FACADE

22. PEAK RESPONSE TIME ~200MSRESPONSE TIMES
NUMBER OF 500S

23. AVAILABILITY
((2XX + 4XX) / ( 2XX + 4XX + 5XX)) * 100
HTTPS://LANDING.GOOGLE.COM/SRE/BOOK/CHAPTERS/EMBRACING-RISK.HTML

24. INCORPORATING
NEW TECHNOLOGY

26. MAINTAINING THE SYSTEM

27. 人 PEOPLE

28. INTRODUCE EVALUATE
ADJUST
PEOPLE LIFECYCLE

29. TRUSTED AUTONOMY

30. TRUST BUT VERIFY

31. APPLICATION REVIEWS

32. BIDIRECTIONAL IDEAS

33. EBB AND FLOW

34. IMPERFECT ARCHITECTURE

35. NON DOGMATIC

36. CREATIVE SOLUTIONS

37. SHARED RESPONSIBILITY

38. GROWTH, DECAY, GROWTH

39. THANK YOU
@BGMARX