Wonder how many sqlite databases would be too many. At one point I assume not all databases can be kept opened at all time. what sort of overhead would there be serving a tenant not opened up yet? there has to be caches etc. not warmed up causing lots of disk IO
defining a unit of processing like duration or quantity and then feeding the algorithm with the equivalent of units consumed (pre or post processing a request) might help.
Thinking this could be useful in a multi tenants service where you need to fairly allocate job processing capacity across tenants to a number of background workers (like data export api requests, encoding requests etc.)
Rally a team around a single goal, get out of the way and let them move fast. If you don't trust your people, you have bigger problems that no methodologies will fix.
the drawback with a subscription is resale value: the next guy will need to buy the subscription too. You cannot recoup the money spent on subscription when you sell your used car.
I literally drilled a hole in the wall underneath the kitchen sink to pass a wire to 2 friends living in the opposite appartement. On campus, you could see wires hanging from window to window outside dorm buildings. Nice times
Don’t. Address the problem correctly. Write good integration tests. Spot the code with corner cases. unit tests these. avoid too much mocks. Docker is your friend