###### tags: `WebHack#39` # Why Microservices? Speaker: Shinichi Hashitani Slides: _TBD_ ## Talk ### Who am I? - Senior Platform Architect --> (Sometimes) Sale Engineer ### Agenda - Microservice Challenges - ### Microsoft Challenge - The first Rule of Software Architecture: --> "Every architectural decision coms with both benefits and trq0iffs," - Fundamentals ![](https://i.imgur.com/xfboPqA.png) - Monolic vs Modualar Monolic ![](https://i.imgur.com/1jlHeVO.png) ### Example of Microservice - ![](https://i.imgur.com/yx3Tkfe.png) ### Keys of microservice - Retry / exception handling - Throttling / back pressuring - Service discovery - Avoid to create service boundry ### Challenge of microservice - API management ![](https://i.imgur.com/sStM0Pw.png) - Back-porting bug fixes - Version like cycle communication ### Something even microservices could be the only way out. - Quote ![](https://i.imgur.com/IUxUxcr.png) - Myth ![](https://i.imgur.com/IPb0ZsH.png) ### Recommended Books ![](https://i.imgur.com/WeiF152.jpg) ## Q & A ## Retrospective ## Networking