Ummm... would characterize an immutable database as a more as a specific use case than general application configuration aka write once, read many traditionall

Ummm... would characterize an immutable database as a more as a specific use case than general application configuration aka write once, read many traditionally for transactional logging/recovery. For concurrent transactions/databases, the immutable stuff does allow for making certain assumptions to improve performance. database management systems typically support/provide front end to multiple/different database engines. As with most things in software world, general situations that allow for customize use case configuration setup, and specific designs/implimentation for specific situations.