Software Applications Should Work Like Restaurants

Transcript

1. Software Applications Should Function Like Restaurants @tourismgeek

2. None
3. None
4. None
5. None
6. None
7. None
8. None

9. Onion Rings Case • Expected volume • Serving fast •

   Least amount of staff resources Caveats • Not the same heat and freshness level

10. Onion Rings Case • Expected volume • Serving fast •

    Least amount of staff compute resources Caveats • Everybody doesn’t get the rings data at the same heat freshness level

11. Steak Case • Why not apply the same model? •

    Serving time is less important • Tuning the 'doneness' level of the steak Caveats • Getting served in longer time

12. Steak Case • Why not apply the same model? •

    Data serving time is less important • Seeing the previous orders correctly is important Caveats • Potentially, getting served in longer time

13. Conclusion • Nothing New • Every Application Data is Not

    the Same • Serve the Data Based On Business Rules

14. Resources • DDD: http://en.wikipedia.org/wiki/Domain-driven_design • Eventual Consistency: http://en.wikipedia.org/wiki/Eventual_consistency • CQRS:

    http://martinfowler.com/bliki/CQRS.html • Blog Post on the Topic: http://goo.gl/eilCVV • Async with ASP.NET MVC (Another Example on the Topic): http://goo.gl/xIImZB