vale | aware linter for prose | Code Analyzer library

Setting up an example:

You can use groupby to apply value_counts after binning the data with pandas.cut:

You can create a new class StateCityCensusDto then also return stateId in your query for censusCitiesByState

Using R1C1 referencing would be easier here:

Should State Changes generated at the read side create more events?

"State changes generated at the read side" is a very... odd... spelling to use in the CQRS pattern.

In the usual arrangement, information from "the outside" is delivered to the write model, and that's where we perform our computation to decide what the new "authoritative" state of the entity is.

The read model is a non-authoritative copy of state; accurate as of some point in the past, but not necessary up to date. Think "cache".

State changes generated by the cache is weird, because the cache is reflection of the write model.

Now, what will sometimes happen, is that we have two models, and the second model will be interested in changes that happen to the first model.

In that case, we use some form of plumbing to connect the outputs of one model to the inputs of the other.

So we have Alice doing her work, and one of the reports (read model) produced by Alice's work becomes one of Bob's inputs as he does his work.

Now, you might -- as a matter of optimization -- broadcast "events" when the caches update, so that subscribers can know that there is information available for processing. But you probably shouldn't be framing these as "state changes" in the sense of being changes to the entities in your domain model. Those changes have already happened, under the governance of the write model.

You are using anchor tab and so your page is getting refreshed. The page refreshes and so the first tab by default is visible again. Try removing the a tag here:

Spring Boot does not know how to convert a String to org.javamoney.moneta.Money. If you are not tied to the format you could provide a @ConfigurationPropertiesBinding and use a config setting like:

If you have several repeated rows you could try using DISTINCT

I was able to get about 25 % faster by combining the three processes.