Anti Patterns and Mistakes Using Serverless (ServerlessConf SF - 08 2018)
- 2. Yochay Kiriatry Principal Program Manager @ Microsoft Azure Bot Service Azure Functions / App Service Technology Advocate Bunch of startups @yochayk yochay@microsoft.com
- 3. We create power point templates based on new visual trends that’s fresh, relevant and always on t h e c u t t i n g e d g e . Dr. Tim Wagner We create power point templates based on new visual trends that’s fresh, relevant and always on t h e c u t t i n g e d g e . Mr. Yochay Kiriaty We create power point templates based on new visual trends that’s fresh, relevant and always on t h e c u t t i n g e d g e . Dr. Peter Sbarski 01 02 03
- 12. Alternative definition from https://en.wikipedia.org/wiki/Algorithm “… a set of rules that precisely defines a sequence of operations."
- 15. F1 F2 F3 F4
- 16. • • •
- 19. ‘invokes’ ValidateInventory via a queue message Orchestrator (ctx.df) keeps track of execution and can be suspended “Standard” programing style (if/else; exceptions; etc.)
- 28. F1 F2
- 29. F1 F2 F3 State
- 31. F1 F3 F2
- 33. Using recursion to artificially extend Function’s execution time beyond current Serverless limits.
- 34. F1 F2
- 35. Using recursion to artificially extend Function’s execution time
- 36. Using recursion to artificially extend Function’s execution time.
- 38. Some API take long time to complete.
- 39. Some API take long time (seconds) rendering clients useless
- 40. API DoWork GetStatus • Execution state
- 41. Some API take long time (seconds) rendering clients useless https://github.com/yochay/serverlesspatterns/tree/master/ASync/src/Azure/JS
- 43. Some API take long time to complete.
- 46. Yochay Kiriatry Principal Program Manager @ Microsoft Azure Functions/ App Service Technical Evangelist / Advocate Bunch of startups https://blogs.msdn.microsoft.com/appserviceteam @yochayk yochay@microsoft.com
- 49. • Azure Queues (SNS/ SQS) are an implementation detail. • No visualization to show relationship between functions. • There is no way to ‘represent’ a group of Function as ‘chained’. F1 F2 F3 F4
- 50. TriggerFunc F1 F2 F3 • Azure Queues (SNS/ SQS) are an implementation detail. • Each individual Function needs to be “aware” of other functions. • Functions need to be idempotent. • Functions need to “DoWork” and “UndoWork”
- 51. TriggerFunc F1 F2 F3 • Azure Queues (SNS/ SQS) are an implementation detail • Central Error Handling Function “understand” the chain/flow Error Handler