I have an application that writes data to database. In case of network breakdowns, the connection to database gets lost & my db queries freezes the whole application.
So, in order to make it asynchronous, I've used a message queue mechanism to separate out the "db queries" part with my "core application part".
The problem is that until the database gets back online, all the data generated in mean time gets lost.
What kind of software design can help to tackle this problem ?