There are relatively few technologies that I adamently refuse to work with in the IT industry.
1. Perl. Fucking hate it. Yes, you *can* write maintainable code with it; and some libraries are surprisingly pleasant to use. Emphasis on "some". That leaves *most* in the category of "out of the question." I simply refuse to work a job where I know ahead of time I'll be using Perl.
1) DO NOT tie our services hard to Google's APIs.
2) DO NOT rely on MQTT. There's no reason whatsoever to not use plain, simple, well-understood HTTPS.
3) DO NOT rely on cloud services. Take it from someone who worked at a cloud provider: JUST SAY NO. Self-host your infrastructure. We don't have the scale to justify cloud services yet.
4) Use the savings from (3) above to hire more local talent.
I was shot down on every ... single ... point.
Every fucking one of them.
Now we're suffering.
Oh, I almost forgot:
5) PULL data, do not push data. Far more reliable, far more flexible, and vastly more bandwidth efficient, especially since compression of bulk data is so much more efficient than piece-meal bits of information.
@vertigo I've run into some cases where pull data was *less* efficient, just because that means you need to poll sometimes, and missing one poll cycle could cause some polls that were previously spaced out over time to come in all at once when the problem is resolved.
take masto for instance. pull federation would be a mess because you can't necessarily hold one connection open per post source at the same time. so you'll poll or flap.
everything else I'm with you 100%.
@falkreon The only sacrifice is loss of real-time response; however, when we came up with the original project vision document, we had worked on a solution to this issue that would have worked well for us. Meanwhile, we're now looking at ways of reducing our network utilization because of the excessive overheads pushing data is causing.
Honestly, that's the least of our worries right now. Right now, I need to figure out why MQTT is damn broken, b/c without that, push vs pull is irrelevant. :(
@vertigo spacecraft use store-and-forward which looks like push to the spacecraft and pull to mission control.
Early bbs's didn't have to deal with single user instances. I have no problems with rss-like systems where ordinary users pull data. Do the same thing with microservers and scaling problems start to appear.
@vertigo this thread is gold. Thank you. I feel your frustration and join you in it.
@rysiek Long live alt.sysadmin.recovery a/k/a Scary Devil Monastary.
Vertigo
Pebbles Pete
Falkreon, when the walls fell
Rysiekúr (old account)
Doc Edward Morbius ❌