I was thinking why would people use B* db instead of other triple stores for a project and what could help in this direction.
The reality is that there are a lot of triple stores each having at least a basic/limited free option. Also many of them are used in production for years and have teams working full time to solve various issues, so this is hard to compete on.
Implementing a cluster for B* (like suggested in other thread )would be a plus but given the development effort I'm not sure it's worth it at this time.
What I mean is that cluster makes no sense before a single instance can support 100M triples(other stores go to 1B) with a good optimizer and a stable API, and maybe a proven production application that works with it.
So the important advantages of B* are license(price), EF api (+optimistic concurency bonus), embeded support, C# code.
B* EF api is an advantage while it doesn't work well with other stores and there are no other Obj-Rdf-Mappers api's in .net. If either of this are fixed most of the advantage is gone.
What I would also consider is integration with SqlServer and graph functions.
In general an application would have at least part of data in relational format (users,roles, etc)
and some in graph format (in triples store or graph db), so the app db is a hybrid.
To solve this problem in .NET world a nice idea is to integrate SQL Server with another db, using clr functions, like suggested
So if B* would have a good integration with SqlServer and graph functions(shortest path, etc) this would mean a great advantage for SqlServer users...most .net world uses sql server anyway.