JSFoo 2017

Most of the current web apps follow Monolithic Architecture i.e. all code (presentation, business and data access layer) is maintained within the same code base.

A micro service is something which is self-contained, well-defined and does not depend on the state of other services. It is a small, independently deployable unit.

So the idea is to explain what are the issues, including performamce, that can happen with a growing monlithic application and how to overcome it using microservices.

Outline

Why do we need Micro-services?
Monolithic Architecture
Performance challenges for growing monolithic application and other shortcomings
Solution: Micro services ?
Transition to Microservices
Technical impact of solution used

Requirements

Understanding of how Monolithic application works

Speaker bio

Mayank is a full-stack developer, with extensive Node.js projects under his hat. He is highly skilled in Node.js, Express, AngularJS, Meteor, PHP (Zend 1 & 2), MySQL, MongoDB, jQuery Google Maps. He is currently part of NodeXperts.
In his free time, he prefers to save humanity/other races, from the jaws of tyrants, with help of his computer and grit. He is a fan of WWE.

Links

• GitHub: https://github.com/mayank-awasthi
• LinkedIn: https://www.linkedin.com/in/mayank-awasthi-b62a0724/
• Facebook: https://www.facebook.com/mayank.lucky
• Blog: http://nodexperts.com/blog/microservice-vs-monolithic/
• StackOverFlow: http://stackoverflow.com/users/1371636/mayank-awasthi
• YouTube: https://www.youtube.com/watch?v=aip5k8AXBJo

Slides

https://www.slideshare.net/NodeXperts/microservice-architecture-part-1