docbox docbox
  • About Mateu
  • Java
  • Kotlin
  • C#
  • Python
  • Design systems
  • Native
  • AI
GitHub repo
to navigate to select ESC to close
  • Create your project

    • Prerequisites
    • Springboot MVC
    • Springboot Webflux
    • Micronaut
    • Quarkus
    • Helidon MP
  • Components

    • Overview
    • Layouts
    • Forms
    • Grids
    • Actions
    • The component tree
    • Supported components
    • Client-side logic
  • Java

    • Getting started
    • Your first Mateu app with Spring Boot
    • Build a real CRUD with relationships
    • Apps and pages
    • Compose a shell with multiple services
    • Declarative vs fluent
    • State, actions and fields
    • Field stereotypes
    • Routing and parameters
    • Examples
    • Foreign keys and options
    • Best practices
    • Triggers and events
    • Microservices example
    • Validation
    • Advanced
    • Rules
    • A real CRUD example
    • Action behavior
    • Navigation and menus
    • Layout and composition
    • UI effects (messages and commands)
    • End-to-end example
  • Java
  • Java
  • Microservices example

Microservices example

Mateu allows each microservice to define and expose its own UI.

Example

@UI("/_users")
public class UsersHome {

    @Menu
    UsersMenu users;
}
public class UsersMenu {

    @Menu
    UsersCrud users;

    @Menu
    RolesCrud roles;
}

What this shows

  • services own their UI
  • UI is not centralized
  • no duplicated frontend layer

Key idea

Backend ownership = UI ownership