3 ms·
> used regularly by only a couple hundred users > completely unnecessary microservices architecture for potential future scaling It sounds like the problem was
by drewcoo 4y ago
> used regularly by only a couple hundred users
> completely unnecessary microservices architecture for potential future scaling
It sounds like the problem wasn't architectural decisions at all. The problems listed are from engineers trying to build for growth that didn't happen. You can probably complain about those because they're your bailiwick.
The root cause is not the engineering side of the house, though. What happened to the predicted growth? A decade ago?
- Taywee 4y agoEvery project here is skunk works. It wasn't made this way in response to growth predictions, but developer fancy. Our entire staff of programmers has never exceeded 5.