The Importance of UI Architecture

[Matt Raible]

Hey guys,

I just read the following article on InfoQ and it seems like there’s some points in here we should consider as we’re developing JHipster 3.0.

http://www.infoq.com/news/2016/02/tilkov-microxchg-human-users

I’m especially intrigued by the Distributed UI Composition comment:

For SPAs, one can split their app into Webpack bundles and lazy-load static files from the parent app. The static bundles are independently served from their respective microservices, and accessed by the client behind a reverse proxy (e.g. Zuul).

Cheers,

Matt

[Julien Dubois]

Hi Matt,

Yes that's something that is very interesting: loading "on the fly" UI components from a micro service. I'm considering using ocLazyLoad for that, but there are many options.

Anyway:

- I'm currently focusing on having one front end on the gateway, as for me this is the most common need: your gateway is a "mashup" of several back-end APIs. And that's why the new microservices don't have a front-end for the moment.

- Then the ability to add new components "on the fly" will come just afterwards, and so microservices will also be able to have front-ends.

It is just me prioritizing stuff, and doing the most important (and probably easiest) stuff first.

Julien.

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/49E041BA-4D6C-4DEE-BE69-B1BD840A83B0%40raibledesigns.com.
For more options, visit https://groups.google.com/d/optout.

--

Julien Dubois

Twitter: @juliendubois
Phone: +33 (0)6 25 02 34 18