matt_oriordan

8 ms·

31.
A real-world introduction to event-driven architecture(ably.com)
4 points by matt_oriordan 5y ago|0 comments
32.
Migrating from Node Redis to Ioredis: a slightly bumpy but faster road(ably.com)
1 points by matt_oriordan 5y ago|0 comments
33.
Periodic Table of Realtime: a compendium for all things event-driven and related(ably.com)
2 points by matt_oriordan 5y ago|0 comments
34.
by matt_oriordan 5y ago
Founder of Ably here That’s odd and clearly a rip off of our post :( Thanks for flagging
35.
WebSockets vs. HTTP(ably.com)
5 points by matt_oriordan 5y ago|0 comments
36.
by matt_oriordan 5y ago
I spent too much time reading HN as opposed to running my business :) Tbh what’s worked best is when I’ve been focussed. Doing many things at once has mostly been the root cause of businesses failing.
37.
Balancing act: the current limits of AWS network load balancers(ably.com)
2 points by matt_oriordan 6y ago|0 comments
38.
by matt_oriordan 6y ago
AWS are reporting that they have an issue with an external provider outside of their network, which may be impacting Internet connectivity between some customer networks and the AP-SOUTHEAST-2 Region. We can confirm that this is indeed havi
39.
by matt_oriordan 6y ago
Amusingly as I read this my tinnitus is hugely amplified and unescapedly present. I have also feared this onset last year may have been caused by my AirPods. Sadly I am unwilling to draw that conclusion based on hundreds of people reporting
40.
by matt_oriordan 6y ago
We have had this same issue. We are migrating from our old ably.io domain to our new domain ably.com. We've been contacting Facebook through public channels, and private channels (our network) for around 7 months, and we're hitti
41.
Achieving exactly-once message processing with Ably(ably.io)
3 points by matt_oriordan 6y ago|0 comments
42.
AWS US East EC2 issues for 8 hours now
3 points by matt_oriordan 6y ago|0 comments
43.
by matt_oriordan 6y ago
Ah, OK, glad I could help :) Out of interest then, what is the reasoning behind the warning about additional latency. Is Google Pub/Sub doing some kind of reconstruction on the receiving end to piece together an unordered stream, or ha
44.
by matt_oriordan 6y ago
This looks like a naive implementation of adding ordering keys on one side, and waiting until all messages arrive on the other in order, without improving the underlying delivery transport to support ordering. From what I can tell, the publ
45.
Delta Compression: A practical guide to diff algorithms and delta file formats(ably.io)
22 points by matt_oriordan 6y ago|0 comments
46.
by matt_oriordan 6y ago
Netlify/Vercel for static site hosting, intercom for chat, SendGrid for mail sending, Ably for pub/sub real-time messaging (yes I’m from ably.com!), paddle for subscriptions as opposed to stripe...
47.
Cassandra counter columns: nice in theory, hazardous in practice(ably.io)
29 points by matt_oriordan 6y ago|0 comments
48.
by matt_oriordan 7y ago
Check out https://guild.co . Quite different to Slack, more like a private professional version of WhatsApp. We use it to communicate with professional groups around topics.
49.
by matt_oriordan 7y ago
How does QUIC or HTTP/3 change things? Polling is polling, regardless of whether it's over HTTP/1, HTTP/2 or HTTP/3 (QUIC).
50.
by matt_oriordan 7y ago
He he, that is true, and not something we're proud of. We're continuing to optimize things where we can with the resources we have. Given our size, we are spending our engineering efforts on our product where we can bring our opti
51.
by matt_oriordan 7y ago
I agree complexity should be avoided. But I don't really follow the logic that if every feature can break security, reliability, etc. you should never change anything or progress. Google is doubling down on these features as you can
52.
by matt_oriordan 7y ago
This feature is not for the Laver Cup, it's for all sports events and scores they have access to, and has been so since 2016 - http://www.thesempost.com/google-adds-live-sports-scores-sea...
53.
by matt_oriordan 7y ago
Sure, but I'm never suggested front-end developers should build new tech every time they want a new feature. But there are solutions to do things better now, so it seems odd to ignore that. It's a bit like saying React/Angula
54.
by matt_oriordan 7y ago
falcolas I am not aware of any single firewall that blocks long polling, or XHR streaming (at least for a fixed period). Can you substantiate that? We regularly check our transports against legacy devices at Ably, so I don't think thi
55.
by matt_oriordan 7y ago
Agreed, and what firewalls block long polling, which is in itself significantly better?
56.
by matt_oriordan 7y ago
Yup, the article covers SSE, long polling and XHR streaming as all vastly superior solutions that would have improved things. So yes :+1:
57.
by matt_oriordan 7y ago
fooblitzky it's interesting you think that handling millions of open websocket connections with state is needed. Firstly, all of these browsers already have connections to Google's servers. HTTP keeps a connection pool open, so k
58.
by matt_oriordan 7y ago
I appreciate when features are in test phase that it makes sense to keep it simple. But this is in production, and there are many dead-simple solutions that do this efficiently, long polling, SSE, etc. This is Google after all.
59.
by matt_oriordan 7y ago
Sure, but long polling and XHR streaming work for all browsers too. The article was not saying you should use Websockets, it was meant to say HTTP polling is the least efficient way possible to do this :)
60.
by matt_oriordan 7y ago
Sure, but that was not the point of the article. It works, but badly, and even long polling would have been a significant improvement and work for every user.

More ›