Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What would be the best way to test for this kind of issues in advance. Testing at theoretical limits at all endpoints?


I'm not sure this falls under testing. If you start with an empty database each time you start the test you may never hit this issue.

I think this is more of a capacity planning issue.


My concern is that even if one plans for a sufficient capacity, there still needs to be testing done to verify that the code actually works if the capacity is nearing the theoretical limit. In this example the database id was transformed into a 32 bit integer somewhere in the application code.

Usually when I hit some sort of unexpected bug in production I try to think about what type of testing will prevent similar problems in the future.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: