The blog excellently outlines the steps to implement optimistic locking in EF Core, from setting up the basic EF Core model to adding a concurrency token and handling concurrency conflicts.

In the context of Entity Framework Core, how can developers implement and rigorously test an optimistic locking strategy in a high-concurrency environment, such as a real-time trading platform, where simultaneous database operations on the same data are not just common but expected? Consider aspects like handling extreme cases of data conflicts, ensuring system resilience under heavy load, and maintaining data consistency without significantly impacting performance.