Tag Info

Hot answers tagged

2

When I have done this sort of thing before - database shared across applications, I find it best to have a single "engine" management service that handles the database - and all apps interface with that. This allows for single place for database code changes - new tables etc - and also managing access, turning on/off application access, security, downtime ...


1

When a flood of messages is received from a particular X (say X1), Y should try and combine the messages (removed duplicates, etc.) without any loss of information and then send the messages at pace that Z would be able to handle. All this while messages from other Xs would be processed (by Y) and be sent to Z.



Only top voted, non community-wiki answers of a minimum length are eligible