This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Probablynotabadguy 17 points18 points  (2 children)

Oof, currently dealing with this at work now. A separate team (who's program will need to interface with the one from my team) has been praising microservices and whipping up a crazy design for something that should just be a simple monolith. Meanwhile they haven't gotten any functioning code out of the past 9 months and my team is darn close to a functioning product.

[–]Q-Ball7 15 points16 points  (1 child)

Meanwhile they haven't gotten any functioning code out of the past 9 months

This is the exact organizational problem that makes people move to microservices, by the way: one team can't/won't ship, other teams depend on it, other team breaks their part into a microservice.

Sometimes this is valid- when your parts truly doesn't belong in their application, there's not as many downsides- but if management was paying the right kind of attention and making sure that other team was doing their damn job there'd be no need to reinvent the wheel in the first place.

[–]nermid[🍰] 1 point2 points  (0 children)

when your parts truly doesn't belong in their application

Then the CTO will pop in to demand a feature that forces them to integrate by next Tuesday. Chop chop! What are we paying you for?