Yea, its always nice to take a step back and look at big picture programming styles like this. As someone who is still learning (will you ever not be in this field?) i'm usually so focused on the details, that its nice to read things like this that take a step back and look at bigger picture idea and project layouts.
It's just refreshing to see a piece that's truly objective. So much of programming feels like an infomercial these days - EVERYTHING YOU KNOW ABOUT ARCHITECTURE IS WRONG, DO THIS!! I mean, there's always been some element of that, but I feel like web development makes it a weekly thing.
I really enjoyed this author's honest pro/con approach that encourages the reader to determine which direction is best for them on their own project.
Where I work we have 2 teams. one with the monolithic unwieldy style, and they are in rut because of it, and my team with the microservice style, and we are in a rut because of the cons mentioned in this article. we are almost out of the rut due to some key changes in approach and some hard talks we've had to have and compromises made but it's been a long slog.
Yea, it does not seem like there is any right answer. Its very contextual, and dependent on individual circumstance. If you ever have a chance to write up a blog post on your experiences, I have no doubt you would have an interested audience here.
Microservice is absolutely essential with more than about 5 devs, or if there are a couple retarded devs. It limits the damage and limits the exponential growth of filthy hacks that would otherwise appear.
6 comments
1 u/ForgotMyName 01 Jul 2015 22:12
Informative and objective, I like it!
1 u/Orbitrix [OP] 01 Jul 2015 22:34
Yea, its always nice to take a step back and look at big picture programming styles like this. As someone who is still learning (will you ever not be in this field?) i'm usually so focused on the details, that its nice to read things like this that take a step back and look at bigger picture idea and project layouts.
0 u/ForgotMyName 02 Jul 2015 16:33
It's just refreshing to see a piece that's truly objective. So much of programming feels like an infomercial these days - EVERYTHING YOU KNOW ABOUT ARCHITECTURE IS WRONG, DO THIS!! I mean, there's always been some element of that, but I feel like web development makes it a weekly thing.
I really enjoyed this author's honest pro/con approach that encourages the reader to determine which direction is best for them on their own project.
0 u/master_blaster 01 Jul 2015 22:15
Where I work we have 2 teams. one with the monolithic unwieldy style, and they are in rut because of it, and my team with the microservice style, and we are in a rut because of the cons mentioned in this article. we are almost out of the rut due to some key changes in approach and some hard talks we've had to have and compromises made but it's been a long slog.
1 u/Orbitrix [OP] 01 Jul 2015 22:51
Yea, it does not seem like there is any right answer. Its very contextual, and dependent on individual circumstance. If you ever have a chance to write up a blog post on your experiences, I have no doubt you would have an interested audience here.
0 u/taxation_is_slavery 02 Jul 2015 00:35
Microservice is absolutely essential with more than about 5 devs, or if there are a couple retarded devs. It limits the damage and limits the exponential growth of filthy hacks that would otherwise appear.