3 ms·
I don’t think you’ll need most of these things. My metric would be whether or not your app would continue to function without these things. Using this metric:
by kotlin2 4y ago
I don’t think you’ll need most of these things. My metric would be whether or not your app would continue to function without these things. Using this metric:
Kill switch: may be required, but unlikely.
Automated deploys: definitely not necessary. Your app can still function if you deploy manually.
CI: definitely not necessary. Your app can still function without automatically run integration tests. It can run without any integration tests at all.
API pagination: depends on the API.
Detailed API logs: not necessary. You can add logging as problems arise. Even when I add detailed logging ahead of time, I often find I missed the one crucial piece of information needed to make using the logs possible during an investigation.
SQL query dashboard: not necessary. You can easily use a script interface or CLI that stores history.
- xapata 4y ago> I often find I missed the one crucial piece of information needed to make using the logs possible during an investigation. This may be a bit of confirmation bias, or ... I'm not sure what the right term is. The times you didn't have the necessary information stick out in your memory, because they were serious problems. The times you did have the right information logged you solved the problem quickly and it never became a fire.
- jaywalk 4y agoThe article describes precisely why proactively adding these things is (probably) necessary. For example, the kill switch: yeah, you hope you won't need it. But if the time comes that you do, it's too late to add it.
- kotlin2 4y agoYou can use that argument when adding anything.