Bilal Cinarli

Independently together: how micro-applications improve developer experience + app performance

Is your monolithic SPA slowing down your developers and your app? Learn how micro-applications can restore speed and autonomy for your teams.

Independently together: how micro-applications improve developer experience + app performance
#1about 3 minutes

Identifying the pain points of monolithic frontend applications

Large monolithic applications often lead to slow deployment pipelines, poor application performance, and frustrating local development environments.

#2about 4 minutes

How monolithic SPAs create dependencies and failures

The combination of monorepos and single-page applications results in monolithic frontends with single points of failure and complex organizational dependencies.

#3about 5 minutes

Deconstructing the monolith into independent applications

Breaking a monolithic SPA into separate applications for each team or feature allows for independent lifecycles and reduces complexity.

#4about 3 minutes

Defining the core principles of micro-application architecture

A micro-application is a small, independent single-page application dedicated to a single page or user flow, with its own runtime and deployment cycle.

#5about 4 minutes

Key benefits of adopting a micro-application approach

This architecture enables independent scaling, better caching, faster load times, quicker local development, and more efficient CI/CD pipelines.

#6about 3 minutes

Managing shared dependencies and breaking changes

Use a shared internal framework and a dedicated developer experience team to manage dependency versions and coordinate breaking changes across applications.

#7about 2 minutes

Sharing UI components and ensuring design consistency

Maintain visual consistency across independent applications by using a shared design system package and including common elements like navigation as micro-frontends.

#8about 3 minutes

Determining when to use the micro-application architecture

This architecture is most beneficial for large organizations with many teams and engineers working on a single product, not for small teams or projects.

#9about 3 minutes

Implementing global layouts and application routing

Global layouts like headers can be shared as packages or micro-frontends, while routing should use URL paths on a single domain to leverage cookies and local storage.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Videos

See all videos
Front-End Micro Apps35:17

Front-End Micro Apps

Serg Hospodarets

Snappy UI needs no Single-Page Application40:24

Snappy UI needs no Single-Page Application

Clemens Helm

Stairway to Heaven - Scaling Frontends the Right Way40:05

Stairway to Heaven - Scaling Frontends the Right Way

Florian Rappl

Destructuring Frontend monoliths with MicroFrontends41:49

Destructuring Frontend monoliths with MicroFrontends

Trishul Goel

Microfrontends at Scale43:20

Microfrontends at Scale

Josh Goldberg

Micro Frontends with Module Federation: Why and How?45:40

Micro Frontends with Module Federation: Why and How?

Manfred Steyer

Micro-frontends anti-patterns40:17

Micro-frontends anti-patterns

Luca Mezzalira

Micro-frontends anti-patterns47:05

Micro-frontends anti-patterns

Luca Mezzalira

From learning to earning

Jobs that call for the skills explored in this talk.

Angular Developer

Angular Developer

Picnic Technologies B.V.
Amsterdam, Netherlands

Intermediate
Senior
RxJS
Angular
TypeScript