danfarrelly

5 ms·

1.
by danfarrelly 1y ago
Inngest ( https://www.inngest.com ) | Engineers, Marketing+GTM | Remote (US, San Francisco) | Full-time | $130-245k + equity Inngest is a developer platform that enables developers to build amazing, complex, and reliable products
2.
by danfarrelly 1y ago
Inngest ( https://www.inngest.com ) | Engineers, Marketing+GTM | Remote (US, San Francisco) | Full-time | $130-245k + equity Inngest is a developer platform that enables developers to build amazing, complex, and reliable products
3.
by danfarrelly 1y ago
You can grab the LLMs-full.txt file here: https://agentkit.inngest.com/llms-full.txt More realtime examples coming soon!
4.
by danfarrelly 2y ago
CTO @ Inngest here. Each event is published with an API key associated with a particular account workspace. We add the workspace id along side the each event in the stream so matches are only evaluated against the matching expressions in a
5.
by danfarrelly 3y ago
How do they handle multi-tenancy for their users? Any post on that?
6.
by danfarrelly 3y ago
We'll also be supporting long-running services as well in the near future which subscribe to updates from Inngest, rather than get invoked via HTTP. Currently, to get beyond the ~5 min limit per step, you'd need to deploy to somet
7.
by danfarrelly 3y ago
This is pretty much what Inngest is ( https://www.inngest.com/ ). Runs on Deno as well.
8.
Building Metrics with TimescaleDB(inngest.com)
4 points by danfarrelly 3y ago|0 comments
9.
Python errors as values: Comparing useful patterns from Rust and Go(inngest.com)
41 points by danfarrelly 3y ago|74 comments
10.
by danfarrelly 3y ago
Our team has just started to use this a bit more and I really liked the .insomnia dir in our projects. This is pretty sad as we've seen this path with Postman - I ~~thought~~ hoped that since Kong had plenty of other viable revenue str
11.
by danfarrelly 3y ago
Thanks! RedwoodJS is fantastic and we've been fortunate to collaborate with the core team to build in some great support for Inngest :) We also collaborated with their core team on a GraphQL envelop plugin that automatically sends even
12.
by danfarrelly 3y ago
Inngest has built in concurrency controls and rate limiting to prevent systems from being overloaded, allowing the user to have the same controls of a traditional worker, but just a simple config option. Inngest was designed to be a solutio
13.
by danfarrelly 3y ago
Funny enough, we were fortunate to meet Guillermo through our lead, GGV as part of due diligence. GGV had recently led Vercel's recent round so he was part of the process of vetting our product. Our timing was also great as we had rece
14.
by danfarrelly 3y ago
Yeah - definitely overlapping use cases! I expanded on more detail above: https://news.ycombinator.com/item?id=36698178
15.
by danfarrelly 3y ago
Hey thanks for the comparison - Temporal is a powerful tool. There are definitely similarities with what Inngest is capable of. Here are a few differences to highlight: - We’ve taken a different approach that removes the queue and worker ab
16.
by danfarrelly 3y ago
Thanks! Fixed :)
17.
by danfarrelly 3y ago
Inngest co-founder here - happy to answer any questions about Inngest or our fundraising!
18.
Inngest helps developers build their back end workflows, raises $3M(techcrunch.com)
7 points by danfarrelly 3y ago|0 comments
19.
by danfarrelly 3y ago
I've seen the demo of this and it's pretty slick! It looks super easy to use and it uses Inngest under the hood which is awesome (I'm one of the co-founders of Inngest [ https://www.inngest.com ] so it's always
20.
by danfarrelly 3y ago
Good question. This was a hard question for us last year and we chose SSPL for the time being as a early stage startup to offer some protection. AGPL allows anyone to deploy your system and re-sell it, but SSPL requires the person to open s
21.
by danfarrelly 3y ago
Exactly - we have many users that have come over after using Temporal. We designed our SDK to be more lightweight and flexible. We want it to feel more just like writing normal code, not a new coding paradigm. For example, you can define st
22.
by danfarrelly 3y ago
This is great - we do capture all logs for each run including any retries, so you can see errors and general successes. All of these other metrics we have internally, but need to expose to our users! Observability is super key for backgroun
23.
by danfarrelly 3y ago
> we had rolled our own monitoring which was itself a PITA to maintain Thanks! What type of monitoring were you looking for? We have some basic metrics now, but know we need to improve this. What metrics, alerting, observability are impo
24.
by danfarrelly 3y ago
This is a great one. I've experienced this myself, especially when you change an event/message and then you need to handle that change in your job/workflow. Things can break pretty easily so you need to have versioning for bo
25.
by danfarrelly 3y ago
We started with TypeScript because it's not well supported with a current solution and none of them support serverless. We wanted to solve serverless first as it's made supporting long-running servers easy. A lot of folks in the T
26.
by danfarrelly 3y ago
Thanks for the comment! what were some of the most painful parts of this at the companies that you worked for?
27.
Show HN: Inngest – Developer platform for background jobs and workflows(inngest.com)
87 points by danfarrelly 3y ago|25 comments
28.
Modern Serverless Job Schedulers(inngest.com)
24 points by danfarrelly 4y ago|6 comments
29.
by danfarrelly 11y ago
Sure! My previous employers were also great places to work, I've been pretty fortunate in my career. I can understand my response may feel generic, if we were having this convo over a coffee or beer, I could tell you in greater detail.
30.
by danfarrelly 11y ago
"an employee could look at that formula after a year and think, "Well, I know where I am now and where I could be in two years, no reason to stay here for that."" The good part about this is that the formula and system i

More ›