> should include optimization of interactions with the load balancer, e.g. where to terminate https, etc.

I'm curious - is there a case where you want to terminate HTTPS on end device instead of (only) on load balancer?

Ignoring any privacy implications, terminating https on the load balancer means the load balancer will use more cpu and memory than if it was just a tcp terminating load balancer or working at layer 2. In a lot of architectures, the load balancer may not have as nice of a failover story as the hosts behind it, minimizing state on the load balancer could make state syncing possible for a quicker failover. If you're running load balancing appliances, those tend to be expensive, so you probably want to let them only do what they have to, so you don't need to buy more of them.

Thanks!

A year is actually not that much for porting such a huge legacy system to a new platform. I imagine most of the work was making the interfaces from/to other platforms.

I think parent was answering the usage of XML in this use case, which is not appropriate. XML has many strengths (as you have outlined), but it has also been (mis/ab)used so many times that it gained bad reputation. What my GGP suggests is an example of such. There is nothing to gain from XML here that any proper DB (with schema) wouldn't offer, or in this case, protobuf.

Kafka logs however are solving a different problem. The mental model is different - they do not record state, but the whole history of transactions, which makes it trivial to change the schema if/when need arises. Saying that the schema should be thought in advance and shouldn't change is not realistic IMHO.

I agree with you, but that is probably something that belongs to a plugin.

Which Chrome for Android does not support.

Then use Firefox for Android.

Which is the same as with anything else really. You need to practice to be good at something.

Ok, allow me to me rephrase GP: will this make it possible (in the long run) to train tensor flow models on AMD acceleration cards in a supported, easy-to-use and performant way, comparable to what NVidia is offering?

I think that's the goal.

The key word is "eventually". CV is making huge progress lately, but it is nowhere near human level yet. My guess would be that the first generation of self-driving cars will use Lidar because it means shorter time-to-market. Later manufacturers will be able to supplement Lidar more and more with cameras + CV. And maybe microphones, thermal cameras,...?

Assuming the LIDAR manufacturers do not achieve regulatory capture to lock out competing tech.

Sure - but I am guessing a few errors here and there would have much less impact than a single programming mistake. Not that I think this is the right way, but I do understand where they come from.

Human error was much more common. But they did have another tool for reconciling trades that was better. It was web based and auto reconciled most things that were obvious matches. I don't recall why, but they were not too concerned with mistakes so long as we could fix them by the end of business. I think it was because that's when clients would see something was off on their statement/account. There was never a concern of losing money. I wish I could remember why, but this is my cumulative experience in banking industry and I quickly forgot everything I learned.

Retention! Always focus on retention. If people keep using your product then you have product market fit. If they keep leaving - you have an uphill marketing battle.

Another consideration is getting customers to come back is vastly easier sell when they liked your product. So, you retention over years can end up significantly longer than the average subscription length.