architecture - Trading applications trade-offs : Databases and low-latency -


To store data, almost all business applications require databases and transactions made on that data. Transactions usually take time to sequence of milliseconds. At the same time, one thing in a business application that is not acceptable, is "latency", therefore, trade-offs in such applications which require upper limit on the time of delay?

For example, a business has been kept by the customer, it must pass some checks, which require the database, a DB. Again, the business should pass in OMS / ORS or Exchange. And, at each level, there will be no need to store any transaction data in the database. How should a balance be maintained between the persistency and low latency of the transaction?

Two things:

  • Caching: Cache rules in your application , So you do not have to hit the database for each business
  • Threading: Keep the code that stores the transaction data in the database in another thread. In this way, you can route the business to the exchange immediately and secure data similar to the database.

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -