gustafnk/microservice-websites

Building consumer-facing websites with multiple teams

microservice-websites's Issues

Conflicting js dependency versions on aggregated pages

What is a good practice to ensure that SPAs from several teams do not use conflicting js library and framework versions? Which are the tradeoffs to make?

Independently developed SPAs rarely use the same version of anything. Three apps from three teams on one page will almost certainly run three different versions of e.g. bootstrap, jquery and some mvc framework, not to mention plugins etc.

Currently the section "local scripts" focuses on load optimization. Do you assume implicitly that the teams coordinate shared versions of libraries, frameworks and plugins and update at a common pace?

Google analytics

...it's nice to now the number of visitors.

Consider using async/defer for script loading

Expand iFrame section in appendix

Headings should be linked to their respective anchor

Add separators between sections

Replace "I" with "we"

http://english.stackexchange.com/questions/24629/use-of-i-we-and-the-passive-voice-in-a-scientific-thesis/24676#24676

Move iFrame section to appendix (or remove it)

Script loading with only ESI

Based on feedback from @AlbertBertilsson

Show how script loading can be done with

• only ESI (script tag sent in response)
• only ESI (using ESI References approach)

Fix responsive styling

• Less margins on mobile devices
• Font size on smaller mobile screens

Draw a "hero image"

Write conclusion

Remove "I" forms

@damoberg

What is the hash in local css and js?

When discussing local css and js, you have a [hash] in several locations. E.g.

"…which after inclusion becomes:

<link rel="stylesheet" href="/shopping-cart/component/style-[hash].css">
<script src="/shopping-cart/component/script-[hash].js"></script>

What does this [hash] mean?

Add ESI caching and dynamic content

It's not just static files that ESI is good for, also quite static or semi-dynamic content (not shopping carts).

De-emphasize h-include in introduction

Show prototype

Hi, thanks for the great post about ESI/CLI. I would like to show you my prototype. Perhaps a great tool to highlight some examples without to run nginx.
https://github.com/hemerajs/momos

List assumptions

• consumer facing site
• "mobile" is as important as "desktop"
• time-to-first-interaction is important
• long-term evolvability primarily comes from possibility to be/become heterogeneous

Style code blocks

• line height
• light grey box

Author, twitter, github, etc etc

Wrong about included CSS references in AJAX responses

I did a mistake about including CSS references (<link rel="stylesheet" src="..." />) in AJAX responses, i.e. fragments used by h-include. It doesn't work, so the approach instead needs to be to use a "loader" (like for JS).

I'll update the text when I have the time...

Fix spelling

"integrations)? we think"

Reported by @damoberg

Change title to "Microservice Websites"

I think it's a better title, since websites are most often consumer facing, while web apps are not as often consumer facing.

Introduce the term 'edge'

Feedback from @perokvist

Clarify ESI performance risks

It doesn't need to be a problem for the page if the transcluded service is down, since ESI have support for exception handling attributes.

However, if the transcluded service has performance problems (server overload or for other reason hangs) the page will hang.

There is a timeout (or similar) attribute, I think, but it would still cause the page to hang for T ms, where T is the timeout length.

Of course, depending on where in the HTML response the hanging ESI element is and if the ESI implementation supports streamed responses (I think Varnish does now?)

Clarify that ESI does not always violate SCS principles

Especially for headers/footers, SEO things, etc...