You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to use Postgres specific data types, either JSON or (prefered?) JSONB. Advantages are quite obvious, as with this change, the database will be aware of content of events, giving the possibility to query by their fields.
However there are few challenges here:
What to do with existing blob data? - since schema will change eventually in the near future, changes will occur this way or another. But changing column data type is more serious action. We could potentially introduce some switch mechanism or try to use event adapters for that.
How combine this approach with surrogates. Personally I don't have an experience with serializing/deserializing json data types between PostgreSQL and .NET, but one of the problems we could possibly need to resolve is conversion of things such as IActorRef to be functional after receiving from database. This is basically an anti-pattern, but it should work nonetheless.
The text was updated successfully, but these errors were encountered:
The idea is to use Postgres specific data types, either JSON or (prefered?) JSONB. Advantages are quite obvious, as with this change, the database will be aware of content of events, giving the possibility to query by their fields.
However there are few challenges here:
IActorRef
to be functional after receiving from database. This is basically an anti-pattern, but it should work nonetheless.The text was updated successfully, but these errors were encountered: