Add a comment

 

Re: Distributed big balls of mud

I think the industry needs a term that differentiates a monolith built as a ball of mud (some definitely are) from those built using a well designed, object oriented, separation of concerns, lowly coupled, component based architecture - i.e. the 'somewhere in the middle' scenario that you mention in your diagram. The trouble is that the microservice junkies have 'framed' the word 'monolith' as something 'bad' when the component oriented 'something in the middle' monolith case is actually micro service/component oriented without the innefficient, unreliable issues of RESTful 'plumbing'. In fact a microservice/component oriented monolith is actually more 'nano' because the granularity can go as low as you like eg., class level, without any ill effect on performance or productivity!

Re: Distributed big balls of mud


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).