The Cracking Monolith: Forces That Call for Microservices

Re:The Cracking Monolith: Forces That Call for Microservices by romanovcode on Wednesday March 22, 2017 @07:13AM (#13929991)

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.

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by kudokatz on Wednesday March 22, 2017 @09:18AM (#13930632)

> 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.

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by markoa on Wednesday March 22, 2017 @11:23AM (#13931638)

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.

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by viach on Wednesday March 22, 2017 @08:42AM (#13930398)

- 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?

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by ec109685 on Wednesday March 22, 2017 @10:50AM (#13931375)

If you reference a null object, an exception is thrown.

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by mehaveaccount on Wednesday March 22, 2017 @08:53AM (#13930461)

"Textbook Mary blog article"?

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by romanovcode on Wednesday March 22, 2017 @08:57AM (#13930493)

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..

[ Parent | on HN ]

Re:The Cracking Monolith: Forces That Call for Microservices by mehaveaccount on Thursday March 23, 2017 @12:01AM (#13937302)

Thanks, useful phrase!

[ Parent | on HN ]