JSFoo is in its ninth edition this year. Talks at JSFoo 2019 will cover the following topics:
- Component architecture – how different web components have been stitched together to build apps; outcomes on UI and performance as a result of architecture choices
- Deployment practices for front-end and how Kubernetes and CI/CD fall into this picture
- Developer experience (DX)
- Functional programming paradigms: ReasonML and ClojureScript
- Privacy and Content Security Policy (CSP)
- New developments such as SvelteJS
Speakers from Razorpay, CloudCherry, Myntra, Innovaccer, GitLab, Microsoft, Atlassian and Gramener will share their work and learnings on these topics.
Who should attend JSFoo:
JSFoo is a conference for practitioners, by practitioners. JSFoo 2019 is a conference for:
- Front-end engineers
- Senior software developers
- Team leaders and engineering managers
- Fullstack developers
- InfoSec professionals
##JSFoo 2019 details:
Dates: 27 and 28 September
Venue: NIMHANS Convention Centre, Bangalore
The following workshops have been curated for before and after the conference:
For inquiries about conference tickets, workshop tickets and any other details, call JSFoo on 7676332020 or email email@example.com
JSFoo 2019 sponsors:
For tickets and sponsorships, contact firstname.lastname@example.org or call +91-7676332020. For queries about proposing talks, write to email@example.com
Breaking Down The Last Monolith
Case of migrating Largescale Angular1.x web application into Service Oriented Frontend Architecture (Aka MicroFrontends) which incorporates AppShell based Architecture.
- What is Micro Frontends ?
- Why it should matter to you ?
- Innovaccer’s Case Study of migrating large angular 1.x application
- Self Contained Systems
We will discuss some of the most popular ways to do the vertical decomposition for the frontend in order to achieve
following objectives while incorporating Service Oriented Frontend Architecture:
- Team Ownership
- Develop Independently
- Run Independently
- Technology Agnostic
- Fast Loading
- Native Support
- Sharing Basics
- Corporate Identity
- Smooth User Interaction
With a monolithic frontend you never get the pliability to scale across groups as assured by microservices. Besides not being able to scale, there is also the classical overhead of a separate backend and frontend team. Each time there is a breaking change in the API of one of the services, the frontend has to be updated. Especially when a feature is added to a service, the frontend has to be updated to ensure your customers can even use the feature.
If you have a frontend small enough it can be maintained by a team which is also responsible for one or more services which are coupled to the frontend. This means that there is no overhead in cross team communication. But because the frontend and the backend can not be worked on independently, you are not really doing microservices.
This talk will describe our experiences, learnings and challenges that we encountered while breaking down our frontend monolith and running it in production since last 18 months.
Need to have basic knowledge of SPA’s and possibly server side rendering.
I am a fullstack engineer who has spent last two years reasearching and enginnering enterprise grade solution for developing resilient large scale application platform for one of the fastest growing Healthcare Platform in United States.
Currently Leading the Node.JS and UI/UX platform at Innovaccer.
5+ years of experience specializing in UI/UX, web application development, backend/infrastructure.
GSoC 2011, 2013