2 ms·
> 1) Make sure devs can run a realistic version of the whole stack locally. This idea is greatly under-appreciated in the industry.
by ericHosick 6y ago
> 1) Make sure devs can run a realistic version of the whole stack locally.
This idea is greatly under-appreciated in the industry.
- jermaustin1 6y agoI'd love to be able to do this where I work, but we have a configuration of our software requires a minimum of 16 machines to work properly. And that is full blown machines, not just tiny dockers or whatever, but our AWS bill is in the 10s of thousands just for our 1 test environment for that setup. That test environment is undersized massively from the production environment, so we can't even do real world load tests against it. It doesn't have the disaster recovery enabled (which would double its size and adds a f5 big-ip load/proxy server in front. We also have a configuration that is more like a single server mode, which is what we primarily develop against on our local setups, but it isn't the exact same functionally, and there are always defects when deploying to the other configuration.