Very related to the eternal discussion of whether the system is build to scale to an imaginary future number of users.
Your NGO story sounds very much like something we’re in the middle of right now – docker compose and some of the developers are beginning to configure a deployment service for pipelines. Any suggestions for a good “worse” way?
Depends of your situation, team size, skills, language, project requirements, expected user base, desired perfs, budget, etc. And of course, type of project.
I'm going to assume you are on a web project, not in a fortune 500 and will have less than 10000 users connected simultaneously. A good rule of thumb is that 99% of companies in this case probably should be keeping a monolith instead of microservice, with Postgres instead of whatever fancy storage they use, a task queue instead of a pipeline and maybe some key/value store just in case.
But honestly, even that can be scaled down in so many cases. You probably can kill the task queue and use threads, forgo the kv store and just live a happy life.
Great article!
Very related to the eternal discussion of whether the system is build to scale to an imaginary future number of users.
Your NGO story sounds very much like something we’re in the middle of right now – docker compose and some of the developers are beginning to configure a deployment service for pipelines. Any suggestions for a good “worse” way?
Depends of your situation, team size, skills, language, project requirements, expected user base, desired perfs, budget, etc. And of course, type of project.
I'm going to assume you are on a web project, not in a fortune 500 and will have less than 10000 users connected simultaneously. A good rule of thumb is that 99% of companies in this case probably should be keeping a monolith instead of microservice, with Postgres instead of whatever fancy storage they use, a task queue instead of a pipeline and maybe some key/value store just in case.
But honestly, even that can be scaled down in so many cases. You probably can kill the task queue and use threads, forgo the kv store and just live a happy life.
YMMV of obviously, so don't blindly apply this.