JSFoo 2019

On component architecture, front-end engineering and Developer Experience (DX)

Monorepo Architecture for production codebase

Submitted by sarthak saxena (@sarthak9thie) on Apr 29, 2019

Section: Full talk (40 mins) Session type: Lecture Technical level: Intermediate Status: Rejected


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)

Example showing how all the modules can reside inside single monorepo(monolith) and dependencies can be resolved (Efficient Way)


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



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/



  • Abhishek Balaji (@booleanbalaji) a year ago

    Hi Sarthak,

    Thank you for submitting a proposal. We need to see detailed slides and a preview video to evaluate your proposal. Your slides must cover the following:

    • Problem statement/context, which the audience can relate to and understand. The problem statement has to be a problem (based on this context) that can be generalized for all.
    • What were the tools/frameworks available in the market to solve this problem? How did you evaluate these, and what metrics did you use for the evaluation? Why did you pick the option that you did?
    • Explain how the situation was before the solution you picked/built and how it changed after implementing the solution you picked and built? Show before-after scenario comparisons & metrics.
    • What compromises/trade-offs did you have to make in this process?
    • What is the one takeaway that you want participants to go back with at the end of this talk? What is it that participants should learn/be cautious about when solving similar problems?

    We need your updated slides and preview video by Jun 8, 2019 to evaluate your proposal. If we do not receive an update, we’d be moving your proposal for evaluation under a future event.

  • Abhishek Balaji (@booleanbalaji) 11 months ago

    Marked as rejected since proposer hasnt responded to comments/updated content before deadline. Will be considered for a future event if content is updated.

Login to leave a comment