Lessons From DAZN: Scaling Your Project with Micro-Frontends

What work are you doing today?

I'm VP of Architecture at a company called DAZN. It's similar to Netflix but for live sports mainly and video-on-demand. It's a platform dedicated to sports. We are available in nine countries and we have a ton of devices that we are targeting between consoles, TVs, set top boxes, web browsers and mobile. I had the possibility to build the application and the platform twice so far. The first version was designed for speed to market. The second version is built for scalability. What I'm sharing in my talks is mainly based on this experience that I find quite unique and it's pretty interesting for me talking about scalability, not only for back-end, but also for front-end.

What's the goal of the talk?

My main aim is trying to provide the experience that we went through in the last two years. I know that currently in the JavaScript community, micro-frontends are a hot topic. Also, many people have a lot of misconceptions around that. And you can read a lot of information online but it is not everything right. I'm trying to shed some light on how we approach micro-frontends for an organization that moved from a single page application to this new architecture with different teams that are working in four different locations in Europe and therefore how we scale our projects and how we overcome several challenges in order to release our application on web and TV devices.

What would the persona be that you are addressing in this talk?

I believe that the perfect attendee for this talk is a tech lead or a senior engineer or a CTO or an architect that is looking at a solution to scale their front-end work. On the back-end, we have ways and consolidated patterns that we can use in order to create distributed systems. On the front-end, there aren't many, and we are exploring them right now and having the possibility to work for more than two years on these projects. Having international exposure allowed us to see the benefits of this approach, I believe that all those roles could benefit a lot from understanding what are the drawbacks and what are the pain points.

What are the actionable takeaways that you'd like the attendees to take from your session?

What I would like to give during my talk is having the possibility to understand that micro-frontends can be a valid solution for the next project that they are working on or for an existing project or product that they are building. The other thing that I believe would be very beneficial for attendees is the fact that I'm going to share insights from the trenches. It's something that I live and breathe with the developers, with the themes, working with them understanding their problems that they're facing and then overcome those problems. All these experiences will be reversed in my talk.