Mirco-frontends And Distributed Component Architecture for Building Modern Web Apps
Over a period of time when building web apps, front-end layer grows and gets more difficult to mantain. Thats what people call a Front-end Monolith. The idea behind micro-frontends is to let individual teams develop apps in a distributed manner without relying on each other and also let them build using the technology/framework they seem fit for the use case. Being technology agnostic, allows teams to choose, change or upgrade frameworks for their apps without worrying about other teams or the whole product. We will dive in and try to understand how micro-frontends work together and how teams can layout process/workflows for smooth development and integration of isolated components.
- Why distributed frontends? Do we really need them?
- Why micro-frontends? - Understanding micro-frontends
- Case Study - Client Project
- Complexity over Usability - Trade offs!
- Isolating components and colloborative development across teams and apps
- Future of Scalable Front-ends
Need to have basic knowledge of SPA’s and possibly server side rendering.
Suroor is the founder of Xencov Software, a technology company based out of New Delhi and previously was the CTO for US based ThinkU gaming startup. He likes to live on the cutting edge of the technology. Regular open-source contributor, speaker at meetups and also a MongoDB certified developer. He brings in massive experience of building scalable web applications using Node.js and has spent last 4 years of his career building web and mobiles games for different geographies. In free time, he likes to travel and often read about international politics.
- Twitter: https://twitter.com/suroorwijdan
- LinkedIn: https://www.linkedin.com/in/suroorwijdan/
- Spoke at JSFoo Pune - https://drive.google.com/file/d/1p2tBhFBQi4WbX1xYiwQJM-Pzwu3MTd8x/view?usp=sharing