We are using Spring Integration DB polling which polls a table every second and executes some logic based on result. My questions are:

  1. What are some good practices we can implement to account for DB load?
  2. The query currently is just simple select, is there anything we can do to improve it (indexes, different query, etc)?

    SELECT id FROM table WHERE status = 'READY' LIMIT 100 FOR UPDATE

  3. Any architectural improvements we could make? Currently, we are thinking of DB Read Replica in AWS.

  • To properly answer this question, we need to know what you're optimizing for. – Robert Harvey Jul 13 '18 at 19:03
  • Is the polling once every second a performance bottle neck/does it cause great load? Have you measured it? Is there an index of the status column? (The database I'm familiar with doesn't allow indexes on string columns.) – Kasper van den Berg Jul 15 '18 at 14:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.