I have used https://github.com/iann0036/iamlive with great success in the past. On high level, the approach you are describing is iamlive on steroids and UX improved.
Wow. That seems to be a succession / resurrection of 2015-2016 projekt I was involved with Norwegian Consumer Council forbrukerrådet and some of major groceries chains(Coop, Rema, NG..)
The moment I left we were receiving soft real-time Pos log data (anonymized) and we’re building some consumer groceries basket stats.
True. Especially if you are an owner and cashier at the said business.
But no so if the cashier is your employee. Keeping track of all small deals and ensuring most of them reaches your bank account and not your employee pocket might appear even bigger problem.
I know some small dining places where profits 3x skyrocketed since they introduced cards payments (in such places most of the profit comes from small things with crazy margins, such as tea or coffee)
And now I have to wonder about negligible performance implications.
Does it mean Google applied point-and-shoot type of fixes in several areas, e.g. OS kernel and hypervisor?
Most likely.
Or. The speculative execution did not provide meaningful performance benefits in the first place? At least for Google workloads?
If so - why all this extra complexity?
It might be something already mentioned below here, on mobile so might miss it.
However, what we do : we use PG role row level access. E.g. each database user has explicitly defined the subset of data ih has access to.
All you need to ensure your application business level views do not mix/confuse logical view of partial data. And! You choose to use correct database user in your back-end data stream/feed.
Have I already mentioned the PG is a great tool and the feature gap between MS Sql, Oracle and PG constantly narrows down as we speak?
Not to sound arrogant. However I think Go (golang) is still in the hype wagon / cargo cult phase.
It's popular as in the "popular latest javascript UI/UX" sense. Not to diminish Go _extraordinary_ achievements, however it's still to early to say.
E.g. Ruby - used to be _mega_ popular, everything was Ruby at some point. Hype is over and it doesn't look too promising. Niche is taken and it stays there.
However part of it's effort is directed into producing tutorials/book material for the educational etc use.
It's obviously up to 100% to them how and where are they going.
From the educational perspective it's _imo_ something worth considering at some point. E.g. combining this collective know-how into some sort of book. I know I would buy it.