AI / Apache Burr Interview questions
Why do Burr’s persister classes follow the b_ naming prefix convention?
Persister classes are named with a b_database-dependency-library pattern (e.g. a persister built on asyncpg lives under a name reflecting that). The b_ prefix exists specifically to avoid clashing with the underlying database client library’s own class or module names when both are imported side by side.
It also leaves room to ship multiple persisters for the same database built on different driver libraries — for example, a Postgres persister built on psycopg versus one built on asyncpg can coexist under distinct, non-colliding names instead of fighting over a single generic PostgresPersister identifier. It is a small convention, but it keeps the persister integrations namespace predictable as more database backends get added.
More Related questions...