Hello all, be gentle, first time posting here.
I need to create a lightweight journaling system, the server will write data to a db, unless there is a connection failure with the db. In that case, it should write changes to a flat file until the db re-connects. Then update the db from the flat file. The db journal is only read in at the re-start of the server, hence why I consider it a journaling system not a real time persistence engine.
What I'm looking for in design
patterns that fit that kind of system, or suggestions in general.
Thanks.