Integration - How to maintain databases in two application in same state at every point of time.

[Community Alums]

Hi Community,

We are integrating the SNOW to third party applications. whenever any case is created in XYZ application we are creating the same case in ServiceNow and based on operation performed in SNOW we are updating. The issue we are facing is whenever the other system is down the data in both application will not be in sync.

We want the integration to be like if update happens it should happen in both end or no update at all. We are using google pubsub as middleware to publish events.

[Amarjeet Pal]

Hello @Community Alums ,

1. I have read about Pub/Sub topics, you can check that once with durable subscriptions to guarantee message persistence even if an XYZ application is down. Messages will be redelivered when the XYZ becomes available.

Also ,

Log errors with relevant details (Messages, ideally responses ) to facilitate troubleshooting and analysis. Set up monitoring to track message processing rates and errors.

Just shared some best practices which we usually use to avoid duplication during down time .

Hope it helps you . thanks

[Community Alums]

Hi Amarjeet

Thanks for your response!

We are republishing the message when other system is down but the records in ServiceNow is already updated (suppose it assigned to some agent) ,but at the same time if customer who is sitting in the other application will see the state as New ( still not assigned) . This is what we dont want at any point of time.