Submitted May 22, 2017

Transition from Monolithic to Microservices Architecture

Section: Full Talk Technical level: Intermediate

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.

Slides

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

Comments

Up next

Service Workers and the Role They Play in Modern-Day Web Apps

Service workers have greatly improved the experience of web apps by providing offline access to pages, caching data, background sync and other native app-like features. Nowadays, Progressive Web Apps are working together with service workers to provide the users better performance and experience than a typical web app. But service worker's power doesn't just stop at giving offline experience and background notifications. They can be used in areas ranging from request deferring to the virtual server.

May 22, 2017

JSFoo 2017