While microservice architectures allowed teams to scale delivery of independently deployable services, most frontend layers are still run as monolithic applications. Similar to server-side applications, frontend layers often grow into large monoliths that are difficult to maintain and evolve. Building, deploying and consuming frontend components across a diversity of teams and web applications can be a daunting task, especially at scale. To address this issue, at OpenTable we enable fast-moving teams to easily build and deploy front-end components using OpenComponents, an open-source, battle tested, front-end microservice architecture for painless component delivery.

The idea behind micro frontends is to enable multiple teams to work seamlessy together by fostering end-to-end ownership of independently developed, tested and deployed features.

Think about UI as the composition of features which are maintained by independent teams. These teams could be cross-functional allowing them to develop such features end-to-end, from a database to user interface and independently deploy them.

During this session I'll explain how OpenComponents works, how do we use it at OpenTable and how we allows teams to build ship and consume frontend components at runtime across teams and web applications at scale.

2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

- The problem: Deploying frontend at scale is non trivial
- A possible solution: infrastructure for publishing/finding/consuming front-end components
- Benefits
- Architectural overview
- Tools
- The OpenTable use case
- Demo: Setting up your private registry, publish and consuming our first component
- Possible applications (sites, html emails, external widgets (think of the like button),..)
- Cons fo this approach and challenges
- Future of microfrontends architectures
- Q&A

Learning Outcome

Understand microfrontend architecture pattern, why and when it could be beneficial to be used.
Be able to implement and adopt open source solution to adopt a microfrontend architecture at scale.

Target Audience

Engineers, devops/techops, architects


Basic html/js knowledge together with node.js.

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Atulya Mahajan

    Atulya Mahajan / Kiran Chhabra - The Subject They Don’t Teach : What’s Post-Deployment

    45 mins
    When we talk about Agile methodologies then focus on just delivery is not enough. There is life beyond delivery, and very often a product makes or breaks its destiny during that phase.
    The Devops process itself is more than Continous Integration/Deployment, and it is important to know the other Cs of Continuous Monitoring and Continuous Operations as well.
    We will share a case study for a team that had to sustain fast-paced releases with a large customer base. Agile, Continuous Integration and Continuous Delivery were not just fads for them but needs for survival.
    This system turned out to be a big success story and thus we went ahead and replicated the model in the rest of the organisation.
  • Liked Rajith Raveendranath

    Rajith Raveendranath - Developer at a Crossroads - Choosing a suitable programming language for Microservices

    Rajith Raveendranath
    Rajith Raveendranath
    Director Quality
    schedule 2 weeks ago
    Sold Out!
    20 mins

    How to choose a suitable programming language for developing Microservices?

    We start our discussion with the most important characteristics of Microservices.

    The following aspects of programming languages are discussed, keeping Microservices in mind:

    • Functional Composition
    • Managing Concurrency
    • Frameworks & Tools
    • Popularity

    We conclude by comparing some popular programming languages using these and drawing some inferences