2 Presentations: Micro Frontends & The road to the Continuous Monitoring

Details

Presentation 1: Micro Frontends: The What, the Why and the How

In this session, Peter Eijgermans focuses on extending the concepts of microservices to the frontend world. This results in Micro Frontends. Microservices is no longer only the latest buzzword but stands for a broad development/paradigm change to Continuous Delivery, RESTful Services and Agile Development. Teams develop independent (micro) services with a private life cycle so that new functionality is placed in a very short space of time in production. For online services such as Netflix and Spotify, this is vital to compete.

Unfortunately, this microservice architecture is only applied to backend development. For the frontend, we mainly build a feature-rich browser application which ends up way too often in the creation of as a single, big frontend-monolith. This problem can be solved with Micro Frontends….

The talk provides answers to the following questions:
What is a good Micro Frontends architecture? What are the integration approaches in the frontend? Why and when to use Micro Frontends? How to build a shared component library in the frontend? How do we speed up development with cross-functional teams? How to speed up development with Micro Frontends? And how do we implement a Micro Frontends in code? (Time for live coding!)

Speaker: Peter Eijgermans
Peter is an adventurous and passionate CodeSmith at Ordina Netherlands. He likes to travel around the world with his bike. Always seeking for the unexpected and unknown. For his job, he tries out the latest techniques and frameworks. He loves to share his experience by speaking at conferences over the World and writing for the Dutch Java magazine and DZone. He believes that you as the front-end developer are the spider in the web to bring the user, the team and the product together.

Presentation 2: The road to the Continuous Monitoring

Is the monitoring up-to-date with current DevOps practices?

Over the 10 years of defined DevOps culture life, we have gone a long road. We have been able to automate almost every step of the delivery process. But we still lack automated monitoring. The transition from the classic way of monitoring to Continuous Monitoring is hard. Not only because it demands very strict approach to the methodology, architecture, etc., but mainly because our organizational culture is not ready for it.

The goal of the presentation is to create a common understanding of what Continuous Monitoring is, what foundations are needed to start building Continuous Monitoring, and what advantages the organizations will gain using it. I am going to go through defined principles, present the MEAL (Metrics, Events, Alerts and Logs), which is my approach to define the structure of Continuous Monitoring and, finally, discuss one of the complex tools to work with.

Aimed with basic principles, the attendees will be able to define areas and best ways to design and implement Continuous Monitoring to their DevOps lifecycle.

Speaker: Paweł Piwosz
He has computers around him for a very long time. My first contact was when I was less than 10 years old, so it gives more than 30 years. Professionally he is involved in the IT industry for over 20 years. He used to work for big companies and small startups. Currently, he is working at Epam as Lead Systems Engineer and helping the organization to grow DevOps practices. Also, he is leading the DevOps Community Poland and he is a member of the BIRD (Be In Real DevOps) movement.

He strongly believes in "DevOps in an Agile way", there is no real DevOps practices without Agile.

His main focus these days is self-development. He is devoted to containers, clouds, serverless, CI/CD, automation tools and monitoring, and he is helping people to understand DevOps.