Best practices for shadow testing services with database write operations

[phadtrapong]

I'm evaluating Diffy for shadow testing a service that performs database write operations. I'm concerned about potential side effects when these operations are mirrored to the shadow service.

Specifically, I'd like to understand:

1. What's the recommended approach for handling database write operations during shadow testing?
2. Are there built-in mechanisms in Diffy to prevent duplicate writes or other side effects?
3. How do other teams typically isolate shadow environments when testing services with persistent state changes?
4. Are there configuration examples for safely testing write operations?

Our service interacts with databases and other downstream systems, and I want to ensure our shadow testing setup doesn't cause unintended effects.

Thanks for your guidance!