The policy bundle were sharded and cached on the client side, so the QPS itself was not much of an impressive data point on the OPA front. On the cache side we were seeing a lot more traffic, ~2B qpm (queries per minute) on daily peaks and p99.9 around 20 us.
I have found OPA to be a fairly reliable and performant system in production. We were able to build a scalable RBAC solution that used OPA as evaluators. We had around 40k OPA instances serving around 350K qps with p99.9 hovering around 6ms.
Definitely, experience matters. However, I am used to an FTC that turns a blind eye on these Pharma antics. So, as long as FTC takes these kind of cases on, I am all for it.
Even the price of generics are way out of line when compared to the generics you get outside of US.
Similarly, a lot of Mergers have resulted in fewer competition in the market, leading to rampant price inflation. Federal institutes like FTC need to step up their game here.
I see that. But without privacy policy, they cannot be held accountable for changes that can be introduced later on.
I checked that there are no backend communication and there are no open websockets. But still kind of scary to use this without a clear Privacy Policy. I love the product by the way :)