malcolp

As a counterpoint, it would be somewhat ironic if the author of a presentation on bloat added middleware to his slides...

You're right there is the same force pushing down on each side. But there's also an additional force in water pushing up. It's called upthrust. It's equal to the weight of displaced water. If the densities are different the samples with the same weight will have different volumes and different upthrusts.

This can be quite a useful phenomenon practically. Anyone who has learned to scuba dive will know that if you take a deep breath in from your air tank you increase your volume without changing your weight and will be able to slightly change your bouyancy and float upwards or downwards without moving your limbs. Submarines also use the same phenomenon.

I love this approach, although I'm yet to work anywhere that does this.

I guess the million (thousand?) dollar questios now become where do you draw the boundary across accounts? Presumably there are many bad ways to slice accounts up. And what happens when accounts do need to communicate?

I can imagine three major scenarios for cross account permissions:

* Cross account iam policies (painful in my experience) * Adding trust policies to enable cross account assuming roles (better but limited) * Limiting cross account policies to specific easy to configure services. E.g. S3 (best option, I've seen but maybe too limited)

Would love to hear the author's view.

I think snowflake supports this.

https://docs.snowflake.com/en/sql-reference/operators-query....

Just googled this and couldn't find any results. Is this a term you came up with?