OrientDB 3中ODatabasePool与OPartitionedDatabasePool无关联的设计疑问

I've run into this exact confusion with OrientDB 3, and it's pretty head-scratching:

• The official manual kicks off by covering OrientDB basics and the ODatabasePool, but if you're already using OPartitionedDatabasePool, forget about switching to ODatabasePool easily.
• Despite their similar names, these two connection pool implementations are totally unrelated—there's no shared interface or compatibility layer between them to enable a smooth transition.

I just can't wrap my mind around why the team designed them this way. From a developer's perspective, it makes perfect sense for these two pools to support seamless switching. They both handle database connection pooling, their naming implies they're part of the same ecosystem family, so you'd expect to be able to swap one out for the other without overhauling your entire codebase. It's a really odd design choice that creates unnecessary friction when adjusting your pooling strategy.

内容的提问来源于stack exchange，提问作者ArjunDhar