Ken has a long history around computers starting with early Commodore PETs and VIC-20s. He is a MongoDB Certified Developer and lives in Oregon with his wife and three children. You can find him mo...
I think it all depends on your application and data design. NoSQL can be incredibly fast for processing but to get the most "bang for your buck" schemas need to be designed differently than they are in a SQL world. It's not a bad thing. It's just a different data modeling style.
In terms of OrientDB performance specifically, it can handle large loads. However, like I just said, the data model is important for top performance. There are many resources available on NoSQL schema design that are well worth the time to read.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it all depends on your application and data design. NoSQL can be incredibly fast for processing but to get the most "bang for your buck" schemas need to be designed differently than they are in a SQL world. It's not a bad thing. It's just a different data modeling style.
In terms of OrientDB performance specifically, it can handle large loads. However, like I just said, the data model is important for top performance. There are many resources available on NoSQL schema design that are well worth the time to read.