Why didn't you mention any of the pros of Monolithic architecture? I thought that was in the table of contents?
Not to mention, Monoliths can decrease productivity in some ways but increase it in other ways; and the same for microservices. Really, the division makes sense based on how you organize your dev teams and how your business units are structured.
Also, it might be useful to talk about Service Oriented Architecture as a whole before just mentioning microservicws straight up. A lot of applications will fall in between; my workplace uses SOA, but we don't use microservices.
Hi, I've briefly said "For years monolithic applications have been industry default because it's simple. All code is in one place, it's simple to test, and deploy." and about service oriented architecture, your right. I should've mentioned that first, I will update the post. Thanks for the feedback!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why didn't you mention any of the pros of Monolithic architecture? I thought that was in the table of contents?
Not to mention, Monoliths can decrease productivity in some ways but increase it in other ways; and the same for microservices. Really, the division makes sense based on how you organize your dev teams and how your business units are structured.
Also, it might be useful to talk about Service Oriented Architecture as a whole before just mentioning microservicws straight up. A lot of applications will fall in between; my workplace uses SOA, but we don't use microservices.
Hi, I've briefly said "For years monolithic applications have been industry default because it's simple. All code is in one place, it's simple to test, and deploy." and about service oriented architecture, your right. I should've mentioned that first, I will update the post. Thanks for the feedback!