5 ms·

I think you already know about this situation because the CTO was in contact with you about it. And it's not really anger, more disappointment. About backups -

I think you already know about this situation because the CTO was in contact with you about it. And it's not really anger, more disappointment. About backups - OrientDB does not backup indexes, it recreates them on restore - but creating indexes is the most expensive operation! For us it meant an unacceptable level of downtime during a restore. The impression I got when I was working with OrientDB is that you focus a lot on features, and OrientDB definitely has a lot of them. So anyone that does a naive point by point comparison with other products will naturally be blown away by OrientDB. But many of these features are not well thought out, or are broken in obvious or subtle ways - e.g. you support Lucene for full text search but it's unusable for anything but the most simple use case. It takes a lot of development time before it becomes apparent just how broken the product is, and that is the problem - if it'd let us down in the first few weeks I wouldn't be writing this. Instead we encountered a constant stream of strange bugs and edge cases, and to be fair to you, you fixed a lot of these problems quickly, but we'd always find new ones, and it became a case of death by a thousand tiny cuts. Nevertheless, because of launch pressure we got into a position where we thought we had something that would suffice, but when we tested it with real world data we got constant lockups and OOM problems. When we realised that one of the most fundamental features - transaction support - was broken, we decided we had no choice but to change data stores and rethink our entire architecture, and to have to do that so late in the game was extremely painful and risky.

lvca 12y ago
Ok, I understand who you are, but it's not fair saying the problems was on OrientDB product: we have a lot of clients running in production without such problems. You used experimental parts like ETL (was still in development) and you guys were aware of this. Furthermore your roadmap was completely unreal, specially managing a new technology that nobody in your company was skilled on. If I was the CTO of your company I'd hire somebody skilled on OrientDB if this would become the foundation of my infrastructure. And you guys didn't model a Graph, but just kept the old model trying hard to let it working with OrientDB. Last but not least, you never paid the renewal and in order to help you we provided support for FREE for 2 months. Sorry, but the main problem there wasn't the product, but the person that worked on this migration. Maybe you lost your job because you wasn't able to do this migration, but please don't put mud on OrientDB.
- anonwarnings 12y ago
  We didn't use the ETL, we rolled our own, and I'm still with the company, so I think you have me confused with someone else. We hired someone who's an OrientDB expert to solve these problems because we assumed that the problem was a lack of skills on our part. Since they were also unable to fix the problems, and since we did run into very real bugs virtually every day, I'm confident that the problem is with the product and not ourselves. We did everything we could to make this work because OrientDB should have been an exact fit for our use case.
  - lvca 12y ago
    Ok, so at this point you wasn't a client and you never hire a real expert? 1) I don't know where did you find this expert. Plugin/driver authors couldn't be certified. Was this expert certified? And why didn't you ask for a certified guy to the Orient Technologies company? 2) Did you ever purchased any professional support from Orient Technologies company?
    - anonwarnings 12y ago
      I think you're more interested in finding out who I am or who I work for and trying to discredit my claims than you are with addressing the issues I raised, so I'm going to decline to answer your questions. This was not an attack on you, although you've taken it as such, I was relating my experiences with your product.

lvca 12y ago

Ok, I understand who you are, but it's not fair saying the problems was on OrientDB product: we have a lot of clients running in production without such problems. You used experimental parts like ETL (was still in development) and you guys were aware of this. Furthermore your roadmap was completely unreal, specially managing a new technology that nobody in your company was skilled on. If I was the CTO of your company I'd hire somebody skilled on OrientDB if this would become the foundation of my infrastructure. And you guys didn't model a Graph, but just kept the old model trying hard to let it working with OrientDB. Last but not least, you never paid the renewal and in order to help you we provided support for FREE for 2 months. Sorry, but the main problem there wasn't the product, but the person that worked on this migration. Maybe you lost your job because you wasn't able to do this migration, but please don't put mud on OrientDB.

anonwarnings 12y ago
We didn't use the ETL, we rolled our own, and I'm still with the company, so I think you have me confused with someone else. We hired someone who's an OrientDB expert to solve these problems because we assumed that the problem was a lack of skills on our part. Since they were also unable to fix the problems, and since we did run into very real bugs virtually every day, I'm confident that the problem is with the product and not ourselves. We did everything we could to make this work because OrientDB should have been an exact fit for our use case.
- lvca 12y ago
  Ok, so at this point you wasn't a client and you never hire a real expert? 1) I don't know where did you find this expert. Plugin/driver authors couldn't be certified. Was this expert certified? And why didn't you ask for a certified guy to the Orient Technologies company? 2) Did you ever purchased any professional support from Orient Technologies company?
  - anonwarnings 12y ago
    I think you're more interested in finding out who I am or who I work for and trying to discredit my claims than you are with addressing the issues I raised, so I'm going to decline to answer your questions. This was not an attack on you, although you've taken it as such, I was relating my experiences with your product.