Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
matt_oriordan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
matt_oriordan
9y ago
Ably realtime | London | Full Time | Onsite or Remote | https://www.ably.io I am the co-founder of Ably realtime, and we're accelerating the growth of our engineering team. Ably helps power next generation digital experienc
92.
▲
Is it time stop calling yourself a developer evangelist?
(medium.com)
5 points
by
matt_oriordan
9y ago
|
0 comments
93.
▲
by
matt_oriordan
9y ago
Ably realtime | London | Full Time | Onsite or Remote | https://www.ably.io I am the co-founder of Ably realtime, and we're accelerating the growth of our engineering team. Ably helps power next generation digital experienc
94.
▲
by
matt_oriordan
9y ago
I ended up buying a second hand MacBook Pro instead of a new one because Apple have stupidly for some reason decided that if you want a more powerful configuration, you have to have a shitty touch bar. It makes no sense, a touch bar and a h
95.
▲
by
matt_oriordan
9y ago
Ably | SDK developer | London head office | Remote (in Europe) | Full time Ably is a global realtime data delivery platform that powers low-latency communication between internet-enabled devices. We solve the hardest parts of delivering th
96.
▲
by
matt_oriordan
9y ago
Ably | DevOps Engineer (remote) | London head office | Remote (in Europe) | Full time If you enjoy the idea of programatically managing infrastructure for a large distributed system and developing network services and layers primarily in Go
97.
▲
by
matt_oriordan
9y ago
Ably | Distributed Systems Engineer (remote) | London head office | Remote (in Europe) | Full time If you enjoy solving truly difficult distributed problems, have Go and Node experience and are looking to work with a deeply technical team t
98.
▲
Distributed systems engineering explained
(blog.ably.io)
1 points
by
matt_oriordan
9y ago
|
0 comments
99.
▲
Rocking horse shit and what it takes to be a distributed systems engineer
(blog.ably.io)
4 points
by
matt_oriordan
9y ago
|
0 comments
100.
▲
by
matt_oriordan
9y ago
Ably realtime | London | Full Time | Onsite and Remote | https://www.ably.io I am the co-founder of Ably and we're accelerating the growth of our engineering team. Ably helps power next generation digital experiences. Ones
101.
▲
by
matt_oriordan
9y ago
Just to confirm, we are not in any way a competitor to Slack, we are a realtime data delivery platform. The article confirms we use Slack ourselves. See www.ably.io/platform for more info.
102.
▲
by
matt_oriordan
9y ago
Please don't troll and have a look at what Ably actually is. It's data messaging, not user / VoIP / chat messaging. We are in no way a competitor to Slack or ever will be. We deliver a platform realtime data delivery. I
103.
▲
by
matt_oriordan
9y ago
Hi Toby Quick responses: > I'm signed into two accounts while the author is signed into 11. Yup. Also, see a subsequent update at https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memor... . One of the Slac
104.
▲
Where's all my CPU and memory gone? the answer: Slack
(medium.com)
9 points
by
matt_oriordan
9y ago
|
1 comments
105.
▲
by
matt_oriordan
9y ago
Ably realtime; London; Full Time; Onsite and remote I am the co-founder of Ably and we're accelerating the growth of our engineering team. Ably helps power next generation digital experiences. Ones which are live rather than static, wh
106.
▲
Universal API for Realtime was not so “universal”, so we forked it
(blog.ably.io)
7 points
by
matt_oriordan
9y ago
|
0 comments
107.
▲
by
matt_oriordan
9y ago
Ably | Full time | Remote | Ideally Europe Ably is a realtime data delivery platform solving distributed problems at scale for businesses like Yahoo, Offerup and Computer Associates. We have our base in London, but mostly work remotely on f
108.
▲
by
matt_oriordan
10y ago
Joel, the point of my article was nothing to do with architecture and using multiple AZs. Of course we use a minimum of two AZs and often three in reach region. The problem is that AWS continued to report the entire region as completely hea
109.
▲
by
matt_oriordan
10y ago
This article was NOT about reliance on a single AZ. That was not the point as we use three AZs in most AWS region, and at least two in every region. The point was simply that an entire AZ was down and Amazon continued to report the entire r
110.
▲
by
matt_oriordan
10y ago
We use three availability zones. Unfortunately that was not the point of the article. The point was one AZ was effectively completely down, yet AWS was reporting the entire region as healthy without any warnings.
111.
▲
by
matt_oriordan
10y ago
That's am impressive bit of technology, and nice to see it's making extensive use of Erlang (we're using Elixir). I'd be interested to know if the service works across multiple regions though. Some of the biggest challen
112.
▲
by
matt_oriordan
10y ago
Read my previous comment. We use multiple AZs. That's not the point of my blog post. I am not complaining about availability of services, I am complaining that there is no accuracy of their service status.
113.
▲
by
matt_oriordan
10y ago
Well it's not that's simple. We do run in multiple availability zones in every region. But if the connectivity between them is partially working, which it was, and shared service from Amazon itself aren't working fully from e
114.
▲
Honest status reporting and AWS service status “truth”
(blog.ably.io)
142 points
by
matt_oriordan
10y ago
|
55 comments
115.
▲
by
matt_oriordan
10y ago
Thanks Justin, I obviously concur!
116.
▲
by
matt_oriordan
10y ago
Hey Sean, Matt here, co-founder of Ably. I have been meaning to write a blog post on this in fact, like I did some time back for ActionCable, see https://blog.ably.io/rails-5-actioncable-the-good-and-bad-pa... . I've no
117.
▲
Hello PubNub and Pusher users – we now speak your language. Welcome to Ably
(ably.io)
41 points
by
matt_oriordan
10y ago
|
14 comments
118.
▲
by
matt_oriordan
10y ago
For those interested, we wrote a blog post about single points of failure with DNS last Friday when the Dyn attack happened. Our strategy ensures our customers are mostly unaffected by issues like this. See https://blog.ably.io&#
119.
▲
by
matt_oriordan
10y ago
This is still affecting us. Our customers on Heroku seem to be the worst affected as Heroku is unable to resolve the DNS
120.
▲
Routing around today's DNS issues
(blog.ably.io)
10 points
by
matt_oriordan
10y ago
|
0 comments
More ›