No, this is a persistence store  implemented using Hibernate. When the cache is updated, it will use Hibernate session to update the database. In case of write-through consistency is guaranteed automatically by Ignite (if cache update fails, it will not update the database, and other way around). If there is a transaction, you can use CacheStoreSession and CacheHibernateStoreSessionListener to maintain ongoing Hibernate transaction and commit it only when the cache transaction is committed (this is also demonstrated in the example).
L2 cache is also supported , but in this case Ignite is plugged into Hibernate and you use Hibernate API to do updates and reads.