Full-stack Microservices

A presentation at Devops DDay in in Marseille, France by William Bartlett

Full-stack Microservices

Full-stack Microservices

whoami?

whoami?

Introduction

Introduction

Microservices

Microservices

Microservices

Microservices

Microservices

Microservices

Microservices

Microservices

Microservices

Microservices

Issue

Issue

Outline

Outline

It’s All Relative

It’s All Relative

Micro Frontends

Micro Frontends

Project Mosaic, Zalando

Project Mosaic, Zalando

OpenComponents, OpenTable

OpenComponents, OpenTable

Metaframework, CanopyTax

Metaframework, CanopyTax

Microservice Websites, Gustaf Nilsson Kotte

Microservice Websites, Gustaf Nilsson Kotte

Other options

Other options

Other options

Other options

Other options

Other options

Other options

Other options

Other options

Other options

Web Components

Web Components

Web Components

Web Components

Demo

Demo

Custom Elements

Custom Elements

It’s an HTML element

It’s an HTML element

Frameworks

Frameworks

Component libraries

Component libraries

Web Components in the Wild

Web Components in the Wild

Atomic Design

Atomic Design

Atomic Design

Atomic Design

Atomic Design

Atomic Design

Atom

Atom

Molecule

Molecule

Organism

Organism

Template

Template

Page

Page

Full-stack Microservices

Full-stack Microservices

Microservices + Web Components

Microservices + Web Components

Web Components + Atomic Design

Web Components + Atomic Design

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Full-stack Microservices

Case Study

Case Study

Conclusion

Conclusion

Conclusion

Conclusion

Conclusion

Conclusion

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Future Work

Today, a microservices architecture allows for developing a very rich application as a composition of decoupled components maintained by autonomous teams, potentially using different technologies. At least that’s true for the back-end. The front-end remains largely monolithic even though various frameworks allow for modular development.

Relying on the technology of Web Components and the principles of Atomic Design, I will demonstrate an application where each microservice provides both front-end and back-end elements. The resulting front-end that the user sees is built merely by composition.

Video

Resources

The following resources were mentioned during the presentation or are useful additional information.

Buzz and feedback

Here’s what was said about this presentation on Twitter.