The current Topology Map (client) implementation has a bunch of down-sides. See HZN-831 for more details.
To write new prototypes or completely replace the existing client side it is crucial to have a solid TopologyService which then is used by a rest component to expose all Topology functionality via REST.
This epic covers the migration from the current state of pure vaadin application to a pure vaadin application using a TopologyService and exposing some functionality via REST, allowing people getting the graphs and also experimenting with new UI concepts.
This epic does not cover migrating all existing features into a rest centric approach (e.g. info panels, breadcrumbs, etc.)