Sep 2019
23 Mon
24 Tue
25 Wed
26 Thu
27 Fri 08:55 AM – 05:00 PM IST
28 Sat 08:55 AM – 05:45 PM IST
29 Sun
Make a submission
Accepting submissions till 21 Sep 2019, 07:20 AM
Sep 2019
23 Mon
24 Tue
25 Wed
26 Thu
27 Fri 08:55 AM – 05:00 PM IST
28 Sat 08:55 AM – 05:45 PM IST
29 Sun
Accepting submissions till 21 Sep 2019, 07:20 AM
JSFoo is in its ninth edition this year. Talks at JSFoo 2019 will cover the following topics:
Speakers from Razorpay, CloudCherry, Myntra, Innovaccer, GitLab, Microsoft, Atlassian and Gramener will share their work and learnings on these topics.
JSFoo is a conference for practitioners, by practitioners. JSFoo 2019 is a conference for:
##JSFoo 2019 details:
Dates: 27 and 28 September
Venue: NIMHANS Convention Centre, Bangalore
##JSFoo workshops:
The following workshops have been curated for before and after the conference:
##Contact details:
For inquiries about conference tickets, workshop tickets and any other details, call JSFoo on 7676332020 or email info@hasgeek.com
#Sponsors:
Click here for the Sponsorship Deck.
Email sales@hasgeek.com for bulk ticket purchases, and sponsoring JSFoo 2019.
#Platinum Sponsor
#Gold Sponsor
#Exhibition Sponsor
#Bronze Sponsor
#Community Sponsor
For tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020. For queries about proposing talks, write to jsfoo.editorial@hasgeek.com
Rahul Gaur
@iamaregee
Submitted Aug 19, 2019
Case of migrating Largescale Angular1.x web application into Service Oriented Frontend Architecture (Aka MicroFrontends) which incorporates AppShell based Architecture.
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:
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
https://docs.google.com/presentation/d/1TCU8eJSgDMJ3uDSSJVtl1FY8OEv5WjkbuZ3EEfe4rZc/edit?usp=sharing
Sep 2019
23 Mon
24 Tue
25 Wed
26 Thu
27 Fri 08:55 AM – 05:00 PM IST
28 Sat 08:55 AM – 05:45 PM IST
29 Sun
Accepting submissions till 21 Sep 2019, 07:20 AM
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}