For example, what I would like to do is to record timestamp of an action taken by one of many the users (singleton action, many possible invokers – synchronization between remote systems).
First thought was to create generic table in DB containing lets say type of data, and actual data in separate columns. At first this seems the right approach but on a larger scale, this can be not that flexible as it should be. If I would need data that should be in separate columns in the future (but this can be stored as separate rows after all)
What would be the best practice to store such shared data? DB gives us nice access isolation levels so race conditions can be avoided without any problems.