Closed bassdread closed 10 years ago
Should the system start if the database is unavailable?
Should the system simply warn that the database is unavailable and gracefully shutdown?
It should probably stay up and wait until the DB becomes available. This way you are not dependent on the order of deployment between Skynet and the DB.
On Apr 30, 2014, at 23:58, "SKYNET.IM" notifications@github.com wrote:
Should the system start if the database is unavailable?
Should the system simply warn that the database is unavailable and gracefully shutdown?
— Reply to this email directly or view it on GitHub.
It should not return 403 when posting data. How about if all returns are made 500?
We now fallback to NEDB (filesystem storage) if no Mongo instance is specified.
No tests to ensure database is available on start up. It runs but fails to return data as there is no database backend.