Avichay Eyal

Tel Aviv, Israel

Avichay Eyal

Fullstack Architect @ Tikal Knowledge

15+ Years of professional web development.
Author of many open source projects covering modern issues and problems in front-end development.

Current sessions

The "nudist" web developer - your browser is your framework

Developers love the idea of having safety nets when they work. The feeling that a stable framework, backed by top software companies and supported by community developers, will ensure they can't go wrong. There is one excellent framework everybody forgets: the web browser.

Using modern web standards, we can add new features/powers into the browser in a snap. Is this too good to be true? Can it be that we are actually at the point where all the shiny component frameworks are disposable? Can we all be freed from the framework fatigue?

The opinionated session will cover the basic ideas of messaging, data binding, component authoring, routing - without dependencies - and compare them with the same features provided by the browser. DYI approach with real code will be presented and compared with features that simply cannot be provided without external tooling.

The following topics will be covered:

- Observables (Using proxies, getters and setters)
- Messaging (Publish-Subscribe)
- Dependency Injection (Using native class mixins)
- Runtime environment variables solution (HTML meta-tags injections)
- Components (Web Components)
- Routing (With Web Components)


One shell to rule them all: Micro-Frontends

The ease at which we are building web applications is increasing over time. Each new framework shows improved capabilities, performance and tools. This is great for developers, with only one "tiny" downside: All frameworks diverge in approach which leads to de-facto inability to switch or change technologies and become less flexible over time.

Micro-Frontends approach enables us to split our products into separate modules as any of them is built with any web technology (i.e. React/Angular/Vue/...). A thin code layer orchestrates them as a single product, keeping the UX intact. The approach enables companies to stale rewrites of old production code and combine new technologies with legacy ones without breaking everything.

On this session we will see how we can orchestrate different modules written in three different technologies to work together as a single application, a true case-study, live demo, tips and tricks for developers to step into this brave new world.

Separating modules and breaking the technology chains enable us to scale up and build products with multiple front-end teams working on different technologies.

We will see the pros and cons of micro-frontends approach and how to deal with side-effects related to development, CI and deployment.