MySql.Data.EntityFrameworkCore vs Pomelo.EntityFrameworkCore.MySql : <p>Which database connector should I use in <strong>.Net Core 2</strong> enterprise level web app which is going to handle large amount of data.</p>

<p>I have two choices:</p>

<ol>
<li>Pomelo.EntityFrameworkCore.MySql</li>
<li>MySql.Data.EntityFrameworkCore</li>
</ol>

<p>But still confuse which one to choose for the development.</p>

<p>I started with <strong>MySql.Data.EntityFrameworkCore</strong>, which is MySQL official provider but after facing several issues while code first migration I had to google again for some better alternative.</p>

<p>After some research I found <strong>Pomelo.EntityFrameworkCore.MySql</strong> bit more helpful for my application and it also covered the issues I was facing before.</p>

<p>But it still left me a bit confuse about which one to choose for long term.</p>

<p><strong>Pomelo</strong> is workign fine currently but I am not sure if they (pomelo team) will keep always keep it updating and will keep it in sync with the latest .Net Core version available in the market??</p>

<p><strong>MySql</strong> is not working as expected but the only plus point with this is : It is provided by MySQl itself.</p>

<p>Please help me to decide</p>
