Hi Luca I would just like to know if the Object Database Interface is going to be deprecated. I cannot determine that from this email thread.
If it is going to be deprecated I think it is good to make an anouncement regarding that so that uncertainty can be avoided. It would be sad to see it deprecated, but I do understand the pressures when it comes to resource allocation. By the way I think OrientDB is a great product. I think you guys are doing great work. Regards Ivanhoe On 9 July 2014 23:45, Luca Garulli <[email protected]> wrote: > Hi Gonçalo, > Thanks for your opinion. OrientDB is trying to do something that other > NoSQL products don't: being an Operational Database with a powerful and > flexible model. We're on the same Gartner Magic Quadrant with the big names > (gartner.com/technology/reprints.do?id=1-1M9YEHW&ct=131028&st=sb), and > OrientDB is the only Graph DBMS perceived as "Operational". > > In facts, most of NoSQL solutions are used as second database (cache, > recommendation only system, etc.), where they get data from a main > Operational DBMS. > > However, this is an Open Source project born from *Underdogs* just for > fun, that one day companies asked for support and training because they > were in Production with OrientDB. So we never claimed to be rock-solid as a > 30-years-engine like Oracle, but if a growing number of users is using > OrientDB there must be a reason. > > Especially because we've non *well written documentation* (nobody in > Orient Technologies is mother tongue, sorry for such childish docs), *poor > examples*, etc., but with a growing number of success stories and big > names as users and partners (soon we'll announce the new world-wide > partners): this means the product must be pretty good from the technical > point of view, otherwise all our users would switch to any other NoSQL > available today with tons of documentation and thousands of Mug as gadgets > in all the IT conference they're present. > > The fact we openly discuss about adopting or loosing an API in the > Community Group, because the main author is too busy to work on, confirm > this is a *Community Driven* product first, then a commercial product for > Enterprises. > > We started from the product, now we're focusing also into the rest, > because we know it's important for adoption and for companies, but step by > step :-) > > Lvc@ > > > > On 9 July 2014 00:18, Gonçalo Luiz <[email protected]> wrote: > >> My very recent opinion is that OrientDB tries to cover a lot of ground >> with very sparse resources. >> >> The concepts thus far implemented are spot on, namely the organic >> organization of nodes and intrinsinc self healing trait that comes with it. >> Really impressive. >> >> However, despite the heroic efforts of the developers, namely Luca, the >> documentation is appaling. It barely scratches the surface of the package >> and is often written in a very poorly way, in a nearly childish way with >> little or no detail. >> >> This makes it absolutely impossible to get the package through a simple >> spike or proof of concept even if my developers love the completude this >> project aims for. I will never be able to secure the funding to become a >> paying customer when the developers waste two days because they couldn't >> create a class type when two nodes were up while everything was ok with >> only one and the thrown exception message was full of typos and referring >> to some internal problem giving no clue on how to get it working. >> >> This is one of the most amazing projects I've ever came across in my 15 >> years of open source development,.but without a serious effort to >> industrialize it, I'm sure it will become a distant memory of a once great >> idea at some point. >> >> Brief and laconic memos sent out to the users don't help at all. Saying >> that one whole layer is now no good to use because ONE developer has quit >> is a huge red flag that put me, and believe a lot of others, out. >> >> I've now dropped all the 66 man day worth of effort I had granted to >> investigate this product in the scope of a multi million dollar project. >> It's really a shame. >> >> A word of advise: if you're not ready yet, that's ok: just state it >> clearly, stick to 0.x versions and don't try to make it look like it's a >> mature product. It fires back. Like today. >> >> Best of luck. >> >> Gonçalo >> On 8 Jul 2014 21:47, "Peter Henzler" <[email protected]> wrote: >> >>> Hi >>> >>> I found OrientDB just a few days ago, when I was looking for a >>> persistence solution for my new project. >>> I found Neo4J and when looking for an alternative that could also be >>> used in commercial products I found OrientDB. >>> >>> I am carrefully studying the APIs and posibilities of OrientDB. >>> Until I read the entries in this forum I was impressed. >>> But when I read from corrupted databases I a shying away! >>> >>> I looked into the ObjectDatabase API and made some test with it. >>> The first thing I didn't like was that when I look at the object >>> instances in the debugger all the instance variables are empty. >>> I have to look in the underlying ODocument object to find the data of >>> the objects properties. >>> Not very suitable for development. >>> >>> The other thing I didn't like is the lack of support for java interfaces. >>> I can not query objects from the database that implement a certain >>> interface. >>> In my opinion a must in serious object oriented programming. >>> Something that is also missing in Neo4J although they have the notion of >>> labels that might be usefull to do this. >>> >>> I have looked in the Sping Data for Neo4J documentation and must admit >>> that they have done a very good job. >>> If I would have the time I would take this project and adapt it for the >>> ObjectDB database system. >>> But unfortunately I haven't. >>> >>> As I have not started working with OrientDB yet, I would be very >>> interested in hearing opinions of other people using the Object Database >>> API. >>> >>> I have a good impression of OrientDB and I think it is a good piece of >>> software. >>> But I do not want to set on a 'dead horse'. >>> I have seen many object oriented databases dieing in the past. >>> So, I do not hope that this is the fate of OrientDB... >>> >>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OrientDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
