You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently evaluating the MongoDB job store for Quartz.NET with the intention of potentially utilizing Azure Cosmos DB in the future, under the assumption that the transition could be as simple as updating the MongoDB connection string to point to Cosmos DB's MongoDB API.
However, I have come across cosmosdb-quartznet library that appears to be specifically tailored for Cosmos DB integration with Quartz.NET. This has prompted some questions:
Is the MongoDB job store fully compatible with Cosmos DB's MongoDB API, and are there any known limitations or considerations we should be aware of?
What are the advantages of using a Cosmos DB-specific library for Quartz.NET over the standard MongoDB job store?
Could you provide insights or guidance on choosing between these two approaches for a Quartz.NET and Cosmos DB integration?
Any information or experiences you can share would be greatly appreciated as we plan our architecture to be both robust and future-proof.
Best regards,
Raj
The text was updated successfully, but these errors were encountered:
Dear Team,
We are currently evaluating the MongoDB job store for Quartz.NET with the intention of potentially utilizing Azure Cosmos DB in the future, under the assumption that the transition could be as simple as updating the MongoDB connection string to point to Cosmos DB's MongoDB API.
However, I have come across cosmosdb-quartznet library that appears to be specifically tailored for Cosmos DB integration with Quartz.NET. This has prompted some questions:
Any information or experiences you can share would be greatly appreciated as we plan our architecture to be both robust and future-proof.
Best regards,
Raj
The text was updated successfully, but these errors were encountered: