Hi Val,

In our legacy system database polling is achieved through a separate table,
let say P, in case employee is updated then a new row gets added to P table
with the primary key of the employee which is updated and then a background
process keeps polling that table for the update.

In new system it will be completely in the grid but for the time being we
have to optimise the legacy system as it is not very resource effective and
during the peak times it just collapse.

What I was thinking if I create a cache with store for this P table is
there any technique which can poll that table with some interval for the
newly added rows and by using bits from our new development we can make
this process improve through ignite

I know its not an ideal use case but just trying to find an optimise way to
achieve the better results for the legacy bits.

Thanks,
Luqman


On 17 Jul 2017 7:18 pm, "vkulichenko [via Apache Ignite Users]" <
[email protected]> wrote:

Hi Luqman,

What exactly do you mean by "new rows"? Is the database updated directly
and you then need to refresh cache with these updates?

-Val

------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://apache-ignite-users.70518.x6.nabble.com/database-
table-polling-tp15006p15027.html
To unsubscribe from database table polling, click here
<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=15006&code=bHVxbWFuYWhtZWRAZ21haWwuY29tfDE1MDA2fC04NjE4NDY2OTY=>
.
NAML
<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/database-table-polling-tp15006p15032.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to