3 ms·

Author without even knowing it described common microservice architecture problems that are faced in front-end. (Because in microservices front-end is consuming

Author without even knowing it described common microservice architecture problems that are faced in front-end. (Because in microservices front-end is consuming API and is usually a SPA) - The single point of fragility Yeah, if you have an js error in your syntax the whole front-end application will not work. - Slow CI Actually the front-end nowadays is the bottleneck of any CI if it is using React/Angular2 because of all the tree-shaking and optimizations. It can take a good 8 minutes to build, optimize, tree-shake, AOT etc. a modern SPA application. - Slow development cycles This has nothing to do with monoliths whatsoever. If your codebase is crap it doesn't matter if it's microservices or monolith. Anyway, I digress since this is a textbook Mary blog article.

viach 10y ago
- Yeah, if you have an js error in your syntax the whole front-end application will not work. How is this possible that you compiled js code with an error during packaging? Or you don't use packaging/analyzers tools?
- ec109685 10y ago
  If you reference a null object, an exception is thrown.
mehaveaccount 10y ago
"Textbook Mary blog article"?
- romanovcode 10y ago
  It's taken from "Disrupted" book. It's basically a blog post that is pure fluff to generate inbound traffic with no real substance. Think "10 ways to increase your Node.JS performance", "3 reasons why your AD Campaign is not working" etc..
  - mehaveaccount 10y ago
    Thanks, useful phrase!
kudokatz 10y ago
> It can take a good 8 minutes to build, optimize, tree-shake, AOT etc. a modern SPA application. Can't you break your SPA into modules that are versioned and build independently to help solve this problem? With additional infrastructure it can also help avoid loading unnecessary code on pages that don't need it, etc.
markoa 10y ago
I have not described nor have hands-on experience with all-in approach to microservices. In our practice all user-facing stuff comes from a monolith. I'd probably argue that fragmenting UI-serving backend so much is not necessary for 99% of teams.

viach 10y ago

- Yeah, if you have an js error in your syntax the whole front-end application will not work. How is this possible that you compiled js code with an error during packaging? Or you don't use packaging/analyzers tools?

ec109685 10y ago
If you reference a null object, an exception is thrown.

mehaveaccount 10y ago

"Textbook Mary blog article"?

romanovcode 10y ago
It's taken from "Disrupted" book. It's basically a blog post that is pure fluff to generate inbound traffic with no real substance. Think "10 ways to increase your Node.JS performance", "3 reasons why your AD Campaign is not working" etc..
- mehaveaccount 10y ago
  Thanks, useful phrase!

kudokatz 10y ago

> It can take a good 8 minutes to build, optimize, tree-shake, AOT etc. a modern SPA application. Can't you break your SPA into modules that are versioned and build independently to help solve this problem? With additional infrastructure it can also help avoid loading unnecessary code on pages that don't need it, etc.

markoa 10y ago

I have not described nor have hands-on experience with all-in approach to microservices. In our practice all user-facing stuff comes from a monolith. I'd probably argue that fragmenting UI-serving backend so much is not necessary for 99% of teams.