Doctrine 2 vs Jugglingdb: What are the differences?
Doctrine 2: An object-relational mapper (ORM) for PHP 5.3.2+ that provides transparent persistence for PHP objects. Doctrine 2 sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL; Jugglingdb: Multi-database ORM: redis, mongodb, mysql, sqlite, postgres, neo4j, memory. JugglingDB(3) is cross-db ORM for nodejs, providing common interface to access most popular database formats. Currently supported are: mysql, sqlite3, postgres, couchdb, mongodb, redis, neo4j and js-memory-storage (yep, self-written engine for test-usage only). Jugglingdb also works on client-side (using WebService and Memory adapters), which allows to write rich client-side apps talking to server using JSON API.
Doctrine 2 and Jugglingdb can be primarily classified as "Object Relational Mapper (ORM)" tools.
Jugglingdb is an open source tool with 1.99K GitHub stars and 268 GitHub forks. Here's a link to Jugglingdb's open source repository on GitHub.