Exposing aggregate’s state by using case class declaration might lead to unintended usage and coupling on the application level. But what about queries? What patterns could you use to expose entity’s raw state only for persistence concerns? Is it pragmatic? Let’s find out.