3 ms·
These weren't fatal to the project or team, but did contribute extra work for net negative value (slower & more maintenance, with no relevant extra features):
by l0b0 2y ago
These weren't fatal to the project or team, but did contribute extra work for net negative value (slower & more maintenance, with no relevant extra features):
- Using Kubernetes to host an application when Docker Compose would do (specialist application with <10 concurrent users).
- Using DynamoDB to store a few kB of temporary data in a processing pipeline, despite having several existing PostgreSQL instances already and no DynamoDB ones.
- konschubert 2y agoThese are complex solutions, not complex problems, though.
- thaumasiotes 2y agoThey are solutions to complex problems. dimal specifically described the behavior of imagining a problem you don't have, and solving it.
- baobabKoodaa 2y agoNo, they are not solutions to complex problems. The problem "how to deploy an application for <10 concurrent users" is not a complex problem.
- thaumasiotes 2y agoYou don't really seem to understand the difference between "a problem you don't have" and "a problem you do have".
- brabel 2y agoI worked on a team for a short while that decided to use Cassandra to store a few hundred thousand accounts, despite the data changing only slowly and being an exact match for a relational database. It was one of the worst choices I've ever seen in my career, and the only reason I could find was that people at the time wanted to learn Cassandra.
- Two9A 2y agoSounds somewhat familiar. I worked at a place that replaced a basic LAMP stack with microservices written in Perl and MongoDB as a backing store, for the sole purpose of raising complexity. And left Mongo on the default settings for the time (speed of return over reliability of saving data), so they ended up with a reporting replica which was MySQL. Don't think I've seen anything before or since which was architected so exactly backwards.
- Gibbon1 2y agoThink my company burned a year on a solution using Cassandra. I think the problem was 1/3 Cassandra and 2/3rds the people that would pick Cassandra amd Java over PostgreSQL and C# or go.
- beryilma 2y agoFor less than 10 concurrent users, I would rather say: - "Using Kubernetes to host an application when NodeJS would do..." I am not very knowledgeable about Kubernetes or Docker, but often times NodeJS+PM2 worked just fine for me for a small user base.
- rswskg 2y agoor you know, a lambda. or fargate. Both much easier than worrying about pm2 or k8s.