Install orientdb with Homebrew, chocolatey

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• orientdb
• orientdb-console
• orientdb-gremlin

Project history

OrientDB was released in 2010, and the GitHub repository was created on 2012-12-09. The official site describes it as the first open-source multi-model NoSQL DBMS combining graph and document capabilities in a scalable operational database.

The project became prominent during the early-2010s NoSQL period, when developers were comparing specialized document stores, graph databases, and key-value engines. OrientDB's pitch was that graph relationships and document flexibility belonged in the same core engine rather than in separate products or adapter layers.

OrientDB Ltd was acquired by CallidusCloud in 2017; SAP announced the acquisition of CallidusCloud in 2018. Later project history includes founder Luca Garulli leaving SAP in 2021 and creating ArcadeDB, an OrientDB-inspired database project, while OrientDB continued as an open-source GitHub project.

Adoption history

OrientDB gained adoption as a general-purpose graph/document database for applications that needed traversals, flexible records, and SQL-like access. The GitHub repository shows several thousand stars and hundreds of forks, and the project received enough attention to appear in academic and industry comparisons of multi-model database performance.

Its adoption story is also a cautionary database-history story: commercial stewardship changed through acquisition, and successors or forks such as ArcadeDB and YouTrackDB later appeared for users interested in related graph and object-oriented models.

How it is used

Developers use OrientDB as an embedded or server database when they want records that can be documents and graph vertices/edges without translating between a document store and a separate graph engine. The docs include administration APIs for creating, dropping, checking, and pooling database connections.

Operators install packages to run OrientDB services and use orientdb-console or related tools for database administration, SQL, graph traversal, schema management, and server configuration. Its configuration files live under ORIENTDB_HOME config paths, making it behave like a traditional Java server package.

Why package nerds care

OrientDB matters to package nerds because it is a heavyweight database packaged as a command-line/server formula, not just a client tool. Installing it brings a Java runtime service, console tools, configuration files, security configuration, and persistent data concerns.

It is also historically notable as a multi-model database package from the first major wave of NoSQL packaging: the same package identity appears across Homebrew and Chocolatey, while upstream provides docs, server binaries, and a large Java repository.

Timeline

• 2010: OrientDB released.
• 2012-12-09: orientechnologies/orientdb repository created on GitHub.
• 2017-09: CallidusCloud acquired OrientDB Ltd.
• 2018-01: SAP announced its acquisition of CallidusCloud.
• 2021-04-29: OrientDB v3.2.0 was announced as generally available in the GitHub discussions.
• 2021-09: Luca Garulli announced ArcadeDB after leaving SAP.

Related projects

• Related database projects include Neo4j, MongoDB, ArcadeDB, and YouTrackDB. Related interfaces and concepts include Gremlin, SQL-like graph traversal, document databases, graph databases, multi-model DBMS design, and Java server deployment.

Sources

• https://api.github.com/repos/orientechnologies/orientdb
• https://dbdb.io/db/orientdb
• https://formulae.brew.sh/formula/orientdb
• https://github.com/orientechnologies/orientdb
• https://github.com/orientechnologies/orientdb/discussions/9595
• https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes
• https://orientdb.dev/
• https://orientdb.dev/docs/3.0.x/misc/Overview.html