Microservices, but what about the UI - Marten Deinum @ Spring I/O 2017

Spring I/O 2017 - 18 -19 May, Barcelona

The last couple of years we have been adopting Microservices but mainly for our backend services. When thinking of the frontend we most of the time end up with a monolithic web application which utilizes our modulair backend.

In this talk we will explore how we could use microservices to our advantage and also split up our frontend so that we can leverage the full power of microservices in both the backend and frontend.

We will explore how the use of some JavaScript techniques combined with progressive enhancement and following web standards help us in creating a modular / Composite UI.

[chrso]

how about security, how to authenticate a request cross applications, how to authorize specific levels of access, how to cross communicate with big amounts of information, so when we go for applications cross communication we tightly couple them and they are supposed to be self contained.

[samgiah]

This approach has many many issues! There are other difficulties that need to be solved than just rendering a page from another server. How do you submit a form? how do you keep the microservice page state? How about navigaton?

[chrso]

If you want to have true self contained applications you need to keep the inter application communication to a minimum so the remain truly self contained, I see greater risk for integration, changing one application could potentially break the other one.

[aammssaamm]

Backend guys should not be allowed at the frontend. They just keep killing it without any clue of what frontend is. This kind of “developement” is a shame.
There is nothing to do with your “javascript skills”, you have no skills in data structure and app architecture.