2 ms·
I have a bot in Java that re-transmits messages between Slack/XMPP/Telegram. Sending message in Slack is: - sent to Slack servers - bot looked up and data se
by dmitriid 6y ago
I have a bot in Java that re-transmits messages between Slack/XMPP/Telegram.
Sending message in Slack is:
- sent to Slack servers
- bot looked up and data sent to it
- bot (on a server in DO) figures out what to do with the message (working with an MQ server running locally :))) )
- sends message back to a server (slack/xmpp/etc.)
- that message gets processed and pushed to the corresponding client
I could never properly measure the time between the original message and the translated message. It was always way way subsecond.
Everything we have now: networks, servers, code is very fast.
[1] Badly written bot here: https://github.com/dmitriid/tetrad https://github.com/dmitriid/tetrad
- oarsinsync 6y ago> I could never properly measure the time between the original message and the translated message. It was always way way subsecond. Everything we have now: networks, servers, code is very fast. All of that said, if the time is measured in more than triple digit nanoseconds, relative to the hardware capabilities that we have today, it’s slow. Please do not take that as a reflection on you personally or your work, but rather a reflection on the layers and layers of abstraction we’ve collectively added, and keep adding. While we’ve made it easier for people (especially developers) to write code, we’ve made everything slower, and just continue to mask that with hardware improvements.
- dmitriid 6y agoI totally agree with you on that conclusion.