Your second point misses an important fact: the Tesla Model S Plaid set a 7:25 Nurburgring lap time, and the Porsche Taycan did it in 7:07. Both of these lap times are faster than many high-performance ICE cars, and close to GT2/3 times which are just below 7:00.
As you might expect, the technology will continue to evolve, too.
Mergent (YC S21 - https://mergent.co) might be precisely what you're looking for in terms of a push-over-HTTP model for background jobs and crons.
You simply define a task using our API and we take care of pushing it to any HTTP endpoint, holding the connection open and using the HTTP status code to determine success/failure, whether or not we should retry, etc.
Ok, I'll bite. We (mergent.co) have looked at similar tools before but ended up managing our own infra. This is primarily because the tools we've found focus on recreating Heroku/similar on our AWS, which doesn't suit our needs.
For example, in addition to traditional applications, we run:
- Kubernetes + Knative
- Apache Pulsar
- ScyllaDB
- Elastic
- Clickhouse (soon)
How would Argonaut help us with our (frankly, painful) infra? We're living in YAML hell over here.
Mergent (YC S21) https://mergent.co -- our crons & background tasks are free for the first 1k invocations per month and pay-as-you-go after that.
There are two ways to set up a cron job: the dashboard or via the API if you need the flexibility, e.g., dynamically creating/starting/stopping crons.
We use HTTP webhooks to make the outgoing cron requests, which makes it easy to integrate with a wide range of services and platforms, including Vercel, Lambda, etc. We're also working on adding local execution so you can have even more control over how your tasks are run without using webhooks, but that's still being built & tested.
Feel free to reply here or email me directly if you have any questions: [email protected]
As you might expect, the technology will continue to evolve, too.