Return 503 instead of blocking if the server/db is highly load

Right now, REST just blocks when trying, for instance, to do a submission, if the database is heavily loaded. If we can catch timeouts on insertion/querying, we can return a "503 Service Unavailable" rather than stay locked and not helping the DB.