tonyhb

10 ms·

31.
by tonyhb 2y ago
There are only a few popular, promoted alternatives to NextJS right now (that I know of): Remix and TanStack. That is, if you're fully React focused, ofc. I dont see promoting Remix as a red flag.
32.
by tonyhb 2y ago
The framework itself is super low overhead. You can deploy this anywhere, and if you deploy to inngest.com the P99 latency of starting agents is sub-50ms (and you can also realtime stream steps, tools, or model responses to the browser). O
33.
by tonyhb 2y ago
The main one is deterministic routing ( https://agentkit.inngest.com/advanced-patterns/routing ). Here's what that means: Each agent builds up state via tool use. On each loop of the network, you inspect this stat
34.
Show HN: AgentKit – JavaScript Alternative to OpenAI Agents SDK with Native MCP(github.com)
64 points by tonyhb 2y ago|15 comments
35.
by tonyhb 2y ago
This is really cool, and PlanetScale Metal looks really solid, too. Always a huge sucker for seeing latency huge latency drops on releases: https://planetscale.com/blog/upgrading-query-insights-to-met... .
36.
by tonyhb 2y ago
This is an LLM response if ever there was one.
37.
by tonyhb 2y ago
It looks like Agents are less about DAG workflows and fully autonomous "networks of agents", but more of a stateful network: * A "network of agents" is a system of agents and tools * That run and build up state (both &qu
38.
by tonyhb 2y ago
Their syntax does look strikingly similar to the API we launched with a couple of years ago: `ctx.run("id", () => {})` vs `step.run("id", () => {})`. It's good to see the ecosystem form around the APIs we&#x27
39.
by tonyhb 2y ago
It's already planned, and rushing out a legal change on a Friday night ahead of plans is less than ideal.
40.
by tonyhb 2y ago
There might be a bit of misunderstanding on what's in that git repo here. It actually contains the executor, state store, queue, and our production UI, plus the syncing, registration, and logic for functions. Earlier this year we didn
41.
by tonyhb 2y ago
Answered this in depth here: https://news.ycombinator.com/item?id=41605220 The TL;DR is both us and Temporal help with durable execution. We layer on events and a differing DX to make things easier, faster, and to also wor
42.
by tonyhb 2y ago
We'll roll out a change that releases source as GPL after 3-4 years next week, actually. I do appreciate these comments and points.
43.
by tonyhb 2y ago
There are similarities with "durable workflows" but, honestly, a completely different approach. Lots of respect for them. A few critical things: * Inngest is primarily event driven. You send an event, we run one or more functi
44.
by tonyhb 2y ago
Our launch week starts on Monday. There's something coming, with a full roadmap for differing DBs, multi-node setups, and metrics :)
45.
by tonyhb 2y ago
Thanks! There are a few things at play. High level, it's important to note we provide infra for you — so our multi-tenancy supports many tenants for every user. In general, fairness means distributing work evenly amongst all accoun
46.
Show HN: Inngest 1.0 – Open-source durable workflows on every platform(inngest.com)
165 points by tonyhb 2y ago|51 comments
47.
by tonyhb 2y ago
Inngest | San Francisco (preferred) + Remote https://www.inngest.com is a modern queueing/durable execution platform that allows all developers to ship fast, reliable code without managing infra, queues, or state. Our users
48.
by tonyhb 2y ago
Inngest | San Francisco + Remote https://www.inngest.com is a modern queueing/durable execution platform that allows all developers to ship fast, reliable code without managing infra, queues, or state. Our users write step
49.
by tonyhb 2y ago
Ah, yes, fair. Someone (and I don't know who) mentioned our company so I did jump in... kind of fair, too. I'l leave this thread :)
50.
by tonyhb 2y ago
We're source available, and a helm chart will be coming soon. We're actually doing the last of any queue migrations now. One of our key aspects is reliability. We were apprehensive of officially supporting self hosting with awkw
51.
by tonyhb 2y ago
Chiming in as the founder of https://www.inngest.com . It looks like Hatchet is trying to catch up with us, though some immediate differences: * Inngest is fully event driven, with replays, fan-outs, `step.waitForEvent` to autom
52.
by tonyhb 2y ago
Disclaimer: I work for Inngest ( https://www.inngest.com ), which works in the same area and released 2 years ago. The restate API is extremely similar to ours, and because of the similarities both Restate and Inngest should work
53.
by tonyhb 2y ago
MLIR is cool and has an exciting future for sure.
54.
by tonyhb 2y ago
Something like Inngest's multi-tenancy aware flow control should be table stakes for most complex products now: https://www.inngest.com/docs/guides/flow-control . Huge disclaimer here: I'm one of the foun
55.
by tonyhb 2y ago
I know Theo. He’s a good person who wants to educate folks, and make things simpler. There are problems with education: you often have to make things contrived to show problems as fast as possible, and it’s hard to convey all of the nuance
56.
by tonyhb 2y ago
Hevy gives you all of this for free, with routines, RIR, rest timers, supersets, 1rm, session, and set volume all easily visible.
57.
by tonyhb 3y ago
No, not given the people who created Redis, built distribution, made it a standard didn’t get paid. Open source isn’t about letting someone else gain from your work. It’s about openness. That’s why it’s of course in AWS’ benefit to support
58.
by tonyhb 3y ago
Yeah, they probably could/should. It'd take a lot to get developer adoption and buy in to a separate product that AWS builds themselves, so they adopted Redis. Easy money. It's easier to piggyback on something that won whi
59.
by tonyhb 3y ago
Fun times ahead! I talked to the Cloudflare team at Clerk's ecosystem hackathon last year, showed them Inngest, and they were really enthusiastic about our model. They said something like "we've been thinking about this for
60.
by tonyhb 3y ago
I suppose it depends on the API. Some languages require grabbing a handle and calling open. Either way, theory is the same!

More ›