Topic Sorting

• initial migration

  • each relation should receive a sorting order

• resilience

  • what happens on programfailure like chain/linking/order gets broken
    do we make a failover?

    • e.g.: delete a link with broken transaction

    • sort shouldn't break if there's an error, do an error msg (seq and seq should send a mail), and return a broken list

    • unit tests for broken lists

    • build defensively

• sort, sort on write and not on read

  • what happens on multiple users?

  • think about lock strategy

  • BenchmarkDotNet for 100/1000/1000 objects in unittest

next steps:

• topic order information into categoryrelations

• sort should happen on EntityCache.Init(), and on write (entitycache and db)