> On Jun 29, 2015, at 10:20 AM, Gal Sagie <gal.sa...@gmail.com> wrote: > > I think there are many open source distributed DB alternatives that can be > plugged > and implement the OVSDB DB operations API and behaviour. > > Ben and Justin, i am interested to know whats your opinion on this > suggestion, > i think now is a good time to consider something like that. > I can say that personally i have heard many supporting opinions from people > regarding this > and would love to know what you guys think about this.
Ben and I discussed this at some length when we were hashing out the design. Our take was that we would start out with ovsdb-server, since we were familiar with the design and could rapidly make changes to improve shortcomings that arose. If we eventually found that it wasn't scaling, we could then switch it out for a different one. At that point, we'd have an understanding of where ovsdb-server worked and where it didn't, and then we'd have better criteria for choosing an alternative. If we choose a different database now, it would almost certainly have its own issues. While the database is clearly a central part of the design, it's integration isn't that complicated, and we should be able to swap it out fairly easily later on. --Justin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
