@Petr Klekner Apologies for the delay repones!
There are several approaches you can take to share a table between services in Azure without using Event Sourcing. Here are a few options:
Azure Cache for Redis: You can use Azure Cache for Redis to store the table data in memory and share it between services. This approach can be fast and efficient, but it can also be expensive depending on the size of the data and the number of requests.
Azure Storage Table: You can use Azure Storage Table to store the table data and share it between services. This approach can be cost-effective, but it can also be slower than using Redis or other in-memory solutions.
Message Broker: You can use a message broker, such as Azure Service Bus or Azure Event Grid, to send updates to the table data between services. This approach can be efficient and scalable, but it can also be more complex to implement and maintain.
SQL Database: You can use a SQL database to store the table data and share it between services. This approach can be reliable and scalable, but it can also be more expensive than using Azure Storage Table or other solutions.
The best approach depends on your specific requirements and constraints, such as the size of the data, the frequency of updates, the performance requirements, and the budget. You may need to experiment with different approaches and evaluate their pros and cons before making a decision.
I hope this helps. Let me know if you have any further questions or concerns.