71–80 of 196 posts
For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the original SDK of the underline services. [1] https://temporal.io/
i.e. pay for what resources you use instead of how many users you have. This is how we pay for AWS/GCP/Azure. I think a lot of dev SaaS could / should go this way.
https://www.nango.dev/ for reference.
[Edit: Added link to Nango website]
For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the original SDK of the underline services. [1] https://temporal.io/
Jumping from free to $50/mo feels like there's a 4.99/9.99 plan missing somewhere. Just because you have 3 people on your team doesn't mean you can casually spare $50 a month, that's a lot of money to the vast majority =( Especially since a project going from one to three, and in the rare case four or five, folks is pretty common, but hitting 10 team members is a serious project milestone. At 10, you're probably also…
^ this here is the reason why I never want to build SaaS products for developers. If you use and benefit from a product that saves time for 3 (usually the most highest paid) employees in the business (developers), you either need re-evaluate how much value this product provides or re-evaluate your business plan.
For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the original SDK of the underline services. [1] https://temporal.io/
Their pricing model is much preferred: https://temporal.io/cloud i.e. pay for what resources you use instead of how many users you have. This is how we pay for AWS/GCP/Azure. I think a lot of dev SaaS could / should go this way.
Earlier quoted context omitted.
Their pricing model is much preferred: https://temporal.io/cloud i.e. pay for what resources you use instead of how many users you have. This is how we pay for AWS/GCP/Azure. I think a lot of dev SaaS could / should go this way.
And if you don't store much inside the workflows themselves - it's quite cheap even if you have hundreds of thousands invocations.
Either "trigger" is a blacklisted word or your domain is on a list somewhere, because my company has this url blocked under the "weapons" category. That's unfortunate.
Earlier quoted context omitted.
^ this here is the reason why I never want to build SaaS products for developers. If you use and benefit from a product that saves time for 3 (usually the most highest paid) employees in the business (developers), you either need re-evaluate how much value this product provides or re-evaluate your business plan.
You have to account that not everyone is working in the US. For someone earning 15k$ per year, 600$ is not little money.
Either "trigger" is a blacklisted word or your domain is on a list somewhere, because my company has this url blocked under the "weapons" category. That's unfortunate.