Author: Sami Ekblad

We recently made a study for new people experiencing using Vaadin for the first time. When finding people who are doing Java web development, many are currently working on Angular applications. The study was very successful and many liked the “Vaadin way”, but we were left with an open question about how to use Vaadin if you are already using Angular?

Angular + Spring Boot projects seem to use a similar team split: backend exposes REST, frontend renders everything. However, many times the UI logic leaks to the backend and suddenly the backend team owns complex grid logic. Every sort order, filter combination, and lazy-loading variant becomes a REST contract negotiation. The frontend team re-implements pagination in TypeScript, or the backend team ships an API designed around the table widget.