arrow_back Learning to learn ReasonML
Developing in a large TypeScript Monorepo arrow_forward
Jira Frontend architecture (r)evolution: a story of mistakes, revelations and human nature
Submitted by Nadia Makarevich (@nadiam) via Zainab Bawa (@zainabbawa) on Monday, 9 September 2019
Section: Full talk (40 mins) Technical level: Intermediate
When jira-frontend repository was born (less than 3 years ago!) Redux was basically a standard for the frontend state management, everyone used it. Jira even built its own architectural guidelines around it and how to build scalable apps with it. And just two and a half years later: drama! Jira and Redux are breaking up, new state management solution involved in it somehow, and the whole Jira frontend architecture is upside down and completely different. Or is it?…
Learn about current Jira Cloud frontend architecture, what is the recommended way to write scalable code in jira-frontend now, what was the problem with Redux and why we abandoned it, and how our architecture guidelines look like today.
This talk will cover:
- A bit of history of frontend in Jira
- How architecture of frontend looked like at the beginning
- How it changed in the following years and why
- How Jira’s frontend architecture looks like today and why
Nadia is a senior developer, tech lead and wanna-be architect from Atlassian. She works in Jira Frontend Platform team, the team that is responsible for the overall architecture of Jira’s frontend, CI/CD pipeline, and building tools and processes for scaling Jira’s frontend development. She is passionate about frontend, architecture and scale, and loves challenges and solving problems that involve all three of them.
In her free time she is wandering around Sydney with a digital camera and pretends to be a pro photographer, learns German for fun, and tries to gather some courage to try surfing this year (which is a bit embarrassing after living in Australia for 3.5 years).