dee | Dee - the DeepLens Educating Entertainer | Speech library

I have a list something like this:

I'm trying to design a double-entry ledger with DDD and running into some trouble with defining aggregate roots. There are three domain models:

1. LedgerLine: individual line items that have data such as amount, timestamp they are created at, etc.
2. LedgerEntry: entries into the ledger. Each entry contains multiple LedgerLines where the debit and credit lines must balance.
3. LedgerAccount: accounts in the ledger. There are two types of accounts: (1) internal accounts (e.g. cash) (2) external accounts (e.g. linked bank accounts). External accounts can be added/removed.

After reading some articles online (e.g. this one: https://lorenzo-dee.blogspot.com/2013/06/domain-driven-design-accounting-domain.html?m=0). It seems like LedgerEntry should be one aggregate root, holding references to LedgerLines. LedgerAccount should be the other aggregate root. LedgerLines would hold the corresponding LedgerAccount's ID.

While this makes a lot of sense, I'm having trouble figuring out how to update the balance of ledger accounts when ledger lines are added. The above article suggests that the balance should be calculated on the fly, which means it wouldn't need to be updated when LedgerEntrys are added. However, I'm using Amazon QLDB for the ledger, and their solutions engineer specifically recommended that the balance should be computed and stored on the LedgerAccount since QLDB is not optimized for such kind of "scanning through lots of documents" operation.

Now the dilemma ensues:

1. If I update the balance field synchronously when adding LedgerEntrys, then I would be updating two aggregates in one operation, which violates the consistency boundary.
2. If I update the balance field asynchronously after receiving the event emitted by the "Add LedgerEntry" operation, then I could be reading a stale balance on the account if I add another LedgerEntry that spends the balance on the account, which could lead to overdrafts.
3. If I subsume the LedgerAccount model into the same aggregate of LedgerEntry, then I lose the ability to add/remove individual LedgerAccount since I can't query them directly.
4. If I get rid of the balance field and compute it on the fly, then there could be performance problems given (1) QLDB limitation (2) the fact that the number of ledger lines is unbounded.

So what's the proper design here? Any help is greatly appreciated!

I have api that return list of workers:

I have little programming experience and have had some issues regarding trying to get said structure to be read as an array.

The code that I have been working on does not seem to output anything at the moment. I want to eventually be able to sort the array, but first I need to actually get an array going.

As you can see below, the Form component is using useFormik hook. The component satisfies all of my needs but I'm struggled when testing comes into play, specially when the form is submitted.

Form.tsx

Suppose you have the following data structure:

I am new to ASP.NET and C#, by looking some tutorial I tried to make a site for voting but the submit button is not working at all, have tried all the solutions given here but still, now it is not working.

Home Controller:

I can run this Teams Bot sample: https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/57.teams-conversation-bot

When I need to add an AudioCard to play a mp3 song, I updated my code:

I have a dataframe that contains groups of people's names in a column as a string. Then I also have a dataframe that contains a list of people's names (1 dataframe row per person's name). Sample dataset as described: