Provide full consistency/tolerance control for MySQL operations

[madonzy]

Hello guys, I just wondering why this is not implemented yet, but I'm happy to provide such a feature if you find it valuable.

Bill Karwin talked about different degrees of tolerance:

• Strict (fetch always from master)
• Time-based (set max allowed lag for slave replication)
• Event-based (some kind of mix session consistency and read-your-writes consistency)
• Lax (lag time is not important)

So for now Magento 2 has only implemented time-based tolerance, but not in the way it supposes to be, it just applies to each query if maxAllowedLag is set in the configuration of the connection.

What do I want to implement? I want each resource model to be able to decide which kind of tolerance degree to use by implementing the appropriate interface so we could be sure that our consistency policy is as much predictable as can be.

Just give the thumb up if you want to have such a future in your Magento 2 projects.

[m2-assistant[bot]]

Hi @madonzy. Thank you for your report. To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[Bar3nho]

This can cause some problems for novice programmers because using it recklessly can easily slow down the master. In general, I find it a very good idea that will provide expected data in a smart way.