HN user

stichers

639 karma
Posts84
Comments46
View on HN
kedro.org 22d ago

Show HN: Kedro as a Service

stichers
8pts2
medium.com 2mo ago

Future-proofing an enterprise agentic platform architecture

stichers
3pts0
medium.com 4mo ago

An agentic workflow pattern for software development

stichers
3pts0
news.ycombinator.com 5mo ago

Evaluations for Testing Agentic AI

stichers
1pts1
news.ycombinator.com 5mo ago

Evaluations in the Real World?

stichers
1pts0
natesnewsletter.substack.com 1y ago

Software 3.0 vs. AI Agentic Mesh: Why McKinsey Got It Wrong

stichers
5pts0
ably.com 3y ago

Choices in AWS network design: VPC peering vs. Transit Gateway

stichers
2pts0
www.nature.com 3y ago

Covid deaths: more than 10M children lost a parent or carer

stichers
4pts0
ably.com 3y ago

Adobe is buying Figma because building collaborative experiences is hard

stichers
6pts0
ably.com 3y ago

Choices in AWS network design: VPC peering vs. Transit Gateway

stichers
7pts1
ably.com 3y ago

How to build a serverless WebSockets platform

stichers
1pts0
www.theguardian.com 3y ago

England must reduce meat intake to avoid climate breakdown, says food tsar

stichers
1pts0
www.theguardian.com 3y ago

The big idea: are we living in a simulation?

stichers
2pts0
ably.com 3y ago

Cloud pubsub services compared: Azure Web PubSub vs. Ably

stichers
13pts1
www.theguardian.com 3y ago

OK. This is fine. UK energy bills forecast to hit £4,266 a year from January

stichers
5pts0
www.nature.com 3y ago

Climate change and unplanned urban sprawl bring more landslides

stichers
2pts0
ably.com 3y ago

Use Next.js and Vercel to build a link-sharing app using serverless WebSockets

stichers
10pts0
www.irishtimes.com 3y ago

The patients who can make doctors wish they weren’t doctors

stichers
1pts0
www.theguardian.com 3y ago

Elon Musk denies reported affair with wife of Google co-founder

stichers
6pts0
www.nature.com 3y ago

How to shrink AI’s ballooning carbon footprint

stichers
2pts0
ably.com 4y ago

A multiplayer ADnD-style game with serverless WebSockets and Azure Functions

stichers
2pts0
www.theguardian.com 4y ago

Three marriages have taught me what true love looks like

stichers
1pts0
www.theguardian.com 4y ago

Petrol profiteering? ‘I’m not robbing motorists, I’m only making 2-3p a litre’

stichers
7pts0
www.theguardian.com 4y ago

I’m nearly 60. Here’s what I’ve learned about growing old so far

stichers
74pts43
ably.com 4y ago

Scale up to a collaborative and multiplayer architecture

stichers
6pts2
newatlas.com 4y ago

Could video games be making kids smarter?

stichers
1pts0
www.theguardian.com 4y ago

Quick ways to make yourself slightly happier

stichers
15pts0
apptrail.com 4y ago

We built a fully regional cloud architecture on AWS

stichers
3pts0
www.oreilly.com 4y ago

Identity problems get bigger in the metaverse

stichers
3pts1
ably.com 4y ago

The realtime web: evolution of the user experience

stichers
83pts28

Yes, it’s amazing how time has flown. I was there for the launch and surely it was just a few months ago.

It is part of LF and is a graduate now after being contributed in 2021.

What nothing we've found out there do (except perhaps kedro) is model the "micro" -- E.G. the specific fine-grained dependencies so you can take a look at your code and figure out how exactly it works.

Just wondering then @elijahbenizzy - how does Hamilton differ from Kedro?

Pretty cool when you're added to a new project, have no idea what people have been working on for the past 2 months there and want to see where most of the actual effort was focused.

That's a neat idea!

That's a good point, but I guess for non-tech people activity => work and no activity => no work, so at that level it illustrates reasonably well, no?

Disclaimer: both the author of the article and the OP for this post (me) work for Ably.

The post compares two cloud pubsub services: Azure Web PubSub and Ably in terms of ease of development, creating a collaborative multi-user pixelart drawing app with both services.

Conclusions: Both Azure Web PubSub and Ably offer a similar pubsub feature set, but the Ably API was easier to use (although comes with the disclaimer that the author has used Ably more in the past).

Being able to publish named events and subscribe to them (client-side) without the need of handling them via an upstream server and custom event handlers was an advantage, while a potential downside is the use of a third party library increases the download size of the app.

I've worked from home for years and agree with much of this. It isn't just the "office at home" it's a totally different mindset. It's probably only in my most recent job that I've really _got_ that, and that is because my company is fully remote so everyone is doing it. Nobody feels left out by being at home, and nobody expects synchronous communication or presenteeism.

Thanks for posting this. Full disclosure: I'm the author. I also work for Ably, which is what the post is about, and I'm a content writer so there is inescapably some marketing in it.

But I hope it's valid because, if you try to build a multi-region system for low-latency data transfer across regions, there are issues like discovery and synchronisation to consider.

I think it may be interesting to see how Ably is architected so its pub/sub messaging is realtime and reliable.

For example, how do the EC2 instances in one region find those in another? How does a published message in one region get to a client subscriber in another?

Short answer is infrastructure for event-driven architecture that is close to the edge so it can distribute events with low latency.

Longer answer is to take a look at some of the Ably blog posts linked in the post here, since they'll explain why Gartner have named this as a category for event-driven brokers.

Thanks for your feedback! I'm not sure I said it's a good user interface (I'm not a visual person so wouldn't have the confidence) but I do think it's a good example of a set of features that show a community interacting in realtime. Maybe I didn't make that clear in the article so I'll bear in mind for future writing. TY!

Thanks for your feedback. Could you elaborate a little? I'm not being snarky -- I came up with them based on similar things I'd seen online and I'm not great at visual communication, so if you've improvement suggestions, I'd genuinely like to hear them.

I'm the author of this article and would appreciate any feedback/thoughts. I included just a few examples on the graphic (mostly from memory as I was lucky enough to come of age in 1990 so lived through it).

I remember when Yahoo mail came along with AJAX and how astonishing it was to not have to refresh to get new mail. Although, over a dial up connection, I'm not sure how "realtime" anything was :)

Were the metrics accidentally omitted?

Not accidentally omitted; we didn't share them because they're not that meaningful without full context of how Ably works internally. The data was useful to the Ably team as they made a decision about whether Graviton would be suitable. It may be possible to share the information anyway if you're interested. I'll find out...

Hey! I'm the author of this article. I work for Ably, so this could be seen as self-promotion but I thought/hope you may find it interesting.

If you want to know more about our Graviton2 migration, or Ably, AMA.

I think it grows on you. There's a way to work with it and if you settle on that, it makes it easier than fighting against the prevailing tide. I find I spend a lot of time looking up opaque build errors but that is partly because the contributing authors aren't all that familiar with it, so their markdown is less than 'pure'

Very helpful - thanks! I completely agree with the calls to action: I've found them inauthentic and jarring. It's a bit like carefully planning an outfit, then throwing some Crocs on at the last minute to serve as footwear! I'm off to spend the rest of my day reading Ken Shirriff's blog :)

Thanks for the post -- I'm the author and came here to put it up.

My goal in writing this was to use an analogy because, although it's not a difficult concept, there are a few variations (broker or not, message stream) and I wanted to pull them all into one explanation.