@russmiles Any thoughts on embedding UI within each microservice? Instead exposing REST and compose in a master web app?
2
2
@arungupta ... the question is does the ui need to evolve separately from the service
1
@russmiles could it? would it?
1
@arungupta it might be a useful option
1
@russmiles theoretically yes, practically? do you know anybody doing that?
2
@arungupta @stilkov has a similar concept of single purpose applications -> innoq.com/blog/st/2014/11/we… // @russmiles
1
1
2
@simonbrown @arungupta @russmiles Yes. I am strongly in favor of viewing UI and backend as one unit (by default)
2
@stilkov how to ensure the experience to user is not patched up UI from silos, esp if different stacks are used? // @simonbrown @russmiles
1
1
@arungupta a standard style guide and set of images, CSS, etc? // @stilkov @russmiles
1
@simonbrown does that work in practice across polyglot stacks? // @stilkov @russmiles
2
Replying to @arungupta
@arungupta @simonbrown @russmiles It works perfectly well. Users value consistent design, SSO, common patterns. A single app isn’t required.

May 20, 2015 · 4:25 PM UTC

1
Replying to @stilkov
@stilkov @arungupta @simonbrown @russmiles I guess in the ideal case a user wouldn't even recognize the app boundaries.