why snapshot is include with an other event and not alone ? There are an exemple how to replay snapshot in domain class ?
regarding throughput - it's 2000 entities per second per partition, as per Azure table performance targets
it's both read/write
and you have 20K entities/sec limit per storage account
but you can shard your streams over storage accounts (pool) to get higher speeds
I thought that's the standard way. But just RecordTypes are much faster
It's an app to calculate and create offers. We decided to change from saving the state to saving the changes as we got problems when we changed the format of the state. So our aggregate is an offer project that contains a bill of quanitites that the user can define. within that there are different positions like RequirementPositionAdded, MaterialPositionAdded. Within those positions there might some inputs like QuantitySet, ItemAddedManually, ItemAddedByReferenceBillOfMaterial. As the UI cannot be completely task based many events will be created. We also had to do a "hack". Instead of ReferenceBillOfMaterialLoaded that contains all items we had to split it to ReferenceBillOfMaterialDataLoaded and per item in the reference bill of material we get a ItemAddedByReferenceBillOfMaterial. Otherwise the data is too big.
And yes it's our first time with DDD and ES and SS ;-)
Any suggestion more than welcome
I'm not familiar with BOM domain
but if takes too long to load your aggregate due to thousands of events in it's stream - snapshots will do the trick.
but it also depends on the size of the events
you can read in 1K events page from Azure
But as you said it's difficult to say if you don't know the domain
don't do snapshots into table storage, use blobs
also you can snapshot into some kind of cache, such as Memcached or Redis
or even on local disks server-side. it's all trade-offs
if BOM is just a collections of positions, Position could be an aggregate of its own
just a stupid idea :smile:
BOM may only track IDs of its Positions and you can load/replay Position streams in parallel
Split it might be a good idea. I just thought that all depending stuff should be in one aggregate/stream but as we do not save our calulation as events that might be possible. Because just the projection/calculation will know that it has to use different positions/aggregates and that should be fine. Thanks for all those new ideas
Hey,
Thanks for the project :) I have a small question about virtual partitions. I'm just trying to understand what the use case / requirement is for virtual partitions. My guess would be that by using virtual partitions, we can write to multiple streams (so long as they're in the same table partition) as part of a single entity group transaction, meaning that if any of the stream write fails we have transactional behaviour. Or maybe it's simply so that multiple streams can be served from the same partition server? Are either of these assumption close to the mark or are there any different reasons / use cases for virtual partitions?
Thanks!
@scottrangerio Hi! Yes, you've got it right! With virtual partitions you may model you whole domain as a single partition while having virtual stream for every aggregate, and you can use ETG. For example you may create stream directory in the same partition and have all operations to be atomic. You may also model simple projections as rows and update them atomically with streams. Some simple apps could be modeled in this way. Think multi-tenant setup where each tenant is a single partition. 2000K entities/sec for partition is more than enough for a majority of event-sourced apps. It is possible to develop simple invoicing multi-tenant app by just using table storage features.
Further optimization is possible by employing actor framework such as Orleans and then batch all write operations to a single partition. It is possible to go very far with this simple technology mix (Streamstone + Orleankka). Add durable sagas (you may try Orleankka's switchable behaviors for this) - and you can develop fairly complex app by just using table storage and some added cleverness :smile:
But I don't know if the CosmoDb API Table is backup with or only DocumentDB Json is backup
yevhen on master
Fuck Russia! 🖕 (compare)
yevhen on master
Fix uploading (compare)
yevhen on master
Add nake script for bash Fix endpoint (compare)
yevhen on master
Fix yml (compare)
yevhen on master
Restore nake first (compare)
yevhen on master
Fix nake command (compare)
yevhen on master
Fix forking (compare)
yevhen on master
Fork azurite process (compare)
yevhen on master
Build azurite (compare)
yevhen on master
Init submodule (compare)
yevhen on master
Switch to Azurite (compare)
yevhen on master
Add azurite as submodule (compare)
yevhen on master
Update build script to Nake V3 (compare)
yevhen on master
Extend gitignore Upgrade to .net6 Update to latest Nake and VS im… (compare)