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
- Accessibility
- 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
##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.
JSFoo 2019 sponsors:
#Platinum Sponsor
 |
 |
|
#Gold Sponsor
 |
|
|
#Exhibition Sponsor
 |
|
|
#Bronze Sponsor
 |
 |
 |
#Community Sponsor
 |
 |
 |
Contact
For tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020. For queries about proposing talks, write to jsfoo.editorial@hasgeek.com
ss
sarthak saxena
@sarthak9thie
Monorepo Architecture for production codebase
Submitted Apr 29, 2019
Section:
Full talk (40 mins)
Technical level:
Intermediate
Session type:
Lecture
A Mono repository is an architectural concept, which basically means all repos in a single repo (clear from its name). Instead of managing multiple repositories of your codebase, you keep all your isolated code parts inside one repository. An isolated part of the code that monorepo has nothing in common with monolithic apps. You can keep many kinds of logical apps inside one repo; for example, a web application having core part with multiple dependent modules or a web app and its react native mobile app sharing a common set of components.
Example showing how different modules are being exported as different GitHub repos inside the main repo (Inefficient way)
https://www.dropbox.com/s/5h5z51eb9qah3qm/Non MonorepoArchiTechTure.png?dl=0
Example showing how all the modules can reside inside single monorepo(monolith) and dependencies can be resolved (Efficient Way)
https://www.dropbox.com/s/7ls8gsdppgdjukw/MonorepoArchiTechture.png?dl=0
Outline
Talk breakup:
- Onboard everyone on the concept of monorepo
- Dive deep into solving architectural problems of the codebase
- Walkthrough the code / Hands-on session
- FAQs / Questionnaires
- Future scope
Requirements
Laptop
Speaker bio
My name is Sarthak Saxena! I am currently working at Playment as a senior Frontend developer. I am a Full stack web developer who strives to marry the love of web and graphic design by finding a harmonious balance between functionality and aesthetics and a very keen problem solver
Linkedin Profile: https://www.linkedin.com/in/sarthaksaxena/
Github: https://github.com/sarthak-saxena/
Links
- Example showing how different modules are being exported as different GitHub repos inside the main repo (Inefficient way)
- https://www.dropbox.com/s/5h5z51eb9qah3qm/Non MonorepoArchiTechTure.png?dl=0
- Example showing how all the modules can reside inside single monorepo(monolith) and dependencies can be resolved (Efficient Way)
- https://www.dropbox.com/s/7ls8gsdppgdjukw/MonorepoArchiTechture.png?dl=0
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}