Composite UI

[colin chalmers]

Hi all,

I've been working with (micro) services for about 6 months now and one of the issues I'm facing at the moment is how to bring the services together in a single composite view.

What strategies or frameworks/tools are others using to do this?
Is that a SPA with Angular/React or some other server-side rendering framework?


Although I see huge benefits in microservices together with event sourcing I see other advantages having a single (monolithic?)  front end in the form of a CMS which already has tooling for layout, user management and access/permissions control. Various microservices would be accessed on the backend

I'm interested in how others are dealing with this

rgds

Colin

[Christian Posta]

If you're using a SPA, then things like angular directives or reactjs components can help. They allow teams to create their own directives and can package them and ship them. The UI would still have to package them all together into a single deployable (that gets shipped to clients browsers, etc). This still ends up being kinda monolithic in terms of its deployments, but you may deploy the UI many hundreds of times a day anyway. 

There are server-side proxy tools for combining UI components at run time (like https://github.com/tes/compoxure/issues).

I would love to see more standardization and implementation of webcomponents (http://webcomponents.org) as I think this is an interesting way to allow teams to create/manage/change their microservices (including UI) with less monolithic deployments. Things like Polymer seem like the right direction.

HTH!

--
You received this message because you are subscribed to the Google Groups "microservices" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microservice...@googlegroups.com.
To post to this group, send email to micros...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microservices/4830f524-851a-4919-b5b6-708e803816c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Christian Posta

twitter: @christianposta

http://www.christianposta.com/blog

http://fabric8.io

[Donnchadh Ó Donnabháin]

  At Newsweaver we're looking at using webcomponents and Polymer to build independently deployable UI services with some common components. It seems promising so far but we're still at the investigation stage.

  Donnchadh

2016-06-22 14:32 GMT+01:00 Christian Posta <christi...@gmail.com>:

If you're using a SPA, then things like angular directives or reactjs components can help. They allow teams to create their own directives and can package them and ship them. The UI would still have to package them all together into a single deployable (that gets shipped to clients browsers, etc). This still ends up being kinda monolithic in terms of its deployments, but you may deploy the UI many hundreds of times a day anyway. 

There are server-side proxy tools for combining UI components at run time (like https://github.com/tes/compoxure/issues).

I would love to see more standardization and implementation of webcomponents (http://webcomponents.org) as I think this is an interesting way to allow teams to create/manage/change their microservices (including UI) with less monolithic deployments. Things like Polymer seem like the right direction.

HTH!

On Wed, Jun 22, 2016 at 12:04 AM, colin chalmers <colin.c...@simplex-it.nl> wrote:

Hi all,

I've been working with (micro) services for about 6 months now and one of the issues I'm facing at the moment is how to bring the services together in a single composite view.

What strategies or frameworks/tools are others using to do this?
Is that a SPA with Angular/React or some other server-side rendering framework?


Although I see huge benefits in microservices together with event sourcing I see other advantages having a single (monolithic?)  front end in the form of a CMS which already has tooling for layout, user management and access/permissions control. Various microservices would be accessed on the backend

I'm interested in how others are dealing with this

rgds

Colin

--

Christian Posta

twitter: @christianposta

http://www.christianposta.com/blog

http://fabric8.io

--

Donnchadh Ó Donnabháin

twitter: @donnchadho

[Jeff]

where is your confusion?  Your essentially describing a composite view.  If i have a service called manufacturer and another called product and i need a view that brings back data combined from both, this is a composite view service.  I call both services from my composite svc, get the data i need, and then combine the into one result.

[Jeff]

another common term for this is an aggregate view.