3 ms·
>Another almost worst thing is having production environments with significantly different stacks to what you are using locally, Everyone has a test environmen
by pixl97 3y ago
>Another almost worst thing is having production environments with significantly different stacks to what you are using locally,
Everyone has a test environment, some people also have a seperate production environment :D
Database/datasize issues typically are the worst here. Dev/UAT environments are typically considered a cost center and you'll commonly see them with some small amount of ram and compute resources. Which is fine when you're testing 'small data'. But if you have enterprise style clients that have hundreds of gigs/terabytes of data, your dev environment behavior is generally going to be very different.
Ran into a case where an enterprise client ran massive db performance problems. We found an unindexed table scan that was killing performance. When doing a post mortem on it, it turns out that 95% of our customers only had around 5 entries in the table. No reason to add an index to that. But this customer had found a neat and interesting workflow that had added thousands of entries to that table.