Just the other day I wrote a DBIx::Class-backed application where the database only has two tables.

What DBIx::Class simplifies a lot is basic CRUD (Create/Read (select)/Update/Delete) operations, as well as stuff like prefetching related tables.

It also has a learning overhead, so the first time you use it, you might spend more time learning it than if you used plain DBI.