workerd

The JavaScript / Wasm runtime that powers Cloudflare Workers (by cloudflare)

Workerd Alternatives

Similar projects and alternatives to workerd

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better workerd alternative or higher similarity.

workerd reviews and mentions

Posts with mentions or reviews of workerd. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-23.
  • Cloudflare Pages: Best server tech since CGI-bin?
    5 projects | news.ycombinator.com | 23 Oct 2022
    The engine is open source: https://github.com/cloudflare/workerd

    We did not create our own engine to create "lock-in". On the contrary, it would be a huge win for us if we could simply run FastCGI or Node or whatever applications unmodified. We'd be able to onboard a lot more customers more quickly that way! Our product is our physical network (with hundreds of locations around the world), not our specific development environment.

    But none of that tech scales well enough that we could run every app in every one of our locations around the world, at an affordable price. Meeting that goal required new tech. The best we could do is base it on open standard APIs (browser APIs, mostly), so a lot of code designed for browsers ports over nicely.

    (I'm the lead engineer for Workers. These were my design choices, originally.)

    5 projects | news.ycombinator.com | 23 Oct 2022
    You can self host the entire Worker runtime if you'd like: https://github.com/cloudflare/workerd
    5 projects | news.ycombinator.com | 23 Oct 2022
  • How to Build Software Like an SRE
    5 projects | news.ycombinator.com | 17 Oct 2022
  • The Future of the Web Is on the Edge
    7 projects | news.ycombinator.com | 6 Oct 2022
    As far as I know Cloudflare Pages Functions with Durable Objects or D1 is the only edge infrastructure that can do this currently. D1 uses SQL as it is built on SQLite, and Durable Objects is used for coordination, but also has a transactional storage API.

    D1 is closed beta, Pages Functions is open beta, but limited to 100,000 requests. You don't need Pages Functions if you have an SPA, it's more of an MPA thing where Workers is used as a server for SSR. It let's you push more work to the server like in the good old days, except the server is a JavaScript runtime running on the edge. Durable Objects is the interesting part, because it gives you the data locality, but also strong consistency.

    Not shilling for Cloudflare, I just think that their stuff is cool and the rest of the industry is definitely playing catch-up to them. You can argue that most of us don't need the scale and it's true, but I would also argue that we can use the performance and the developer convenience, and especially the convenience. Their runtime is also open-source, which is nice.

    https://blog.cloudflare.com/workerd-open-source-workers-runt...

  • 10 Trending Github repositories / October, 6 2022
    9 projects | dev.to | 6 Oct 2022
    git clone https://github.com/cloudflare/workerd.git
  • Show HN: Postgres WASM
    16 projects | news.ycombinator.com | 3 Oct 2022
  • Workerd: The Open Source Cloudflare Workers Runtime
    7 projects | news.ycombinator.com | 27 Sep 2022
    Thank you! But for the record there are at least 56 people who contributed to this code and they all deserve credit. :)

    https://github.com/cloudflare/workerd/commit/a265d5c22bf2a6b...

    7 projects | news.ycombinator.com | 27 Sep 2022
    The config format is defined and documented here:

    https://github.com/cloudflare/workerd/blob/main/src/workerd/...

    We definitely need to provide more higher-level documentation around this, which we're working on, but if you're patient enough to read the schemas then everything is there. :)

    To act as a proxy, you would define an inbound socket that points to a service of type `ExternalServer`. There are config features that let you specify that you want to use proxy protocol (where the HTTP request line is a full URL) vs. host protocol (where it's just a path, and there's a separate Host header), corresponding to forward and reverse proxies.

    Next you'll probably want to add some Worker logic between the inbound and outbound. For this you'd define a second service, of type `Worker`, which defines a binding pointing to the `ExternalServer` service. The Worker can thus send requests to the ExternalServer. Then you have your incoming socket deliver requests to the Worker. Voila, Workers-based programmable proxy.

    Again, I know we definitely need to write up a lot more high-level documentation and tutorials on all this. That will come soon...

    7 projects | news.ycombinator.com | 27 Sep 2022
  • A note from our sponsor - Zigi
    www.zigi.ai | 26 Nov 2022
    Zigi makes context switching a thing of the past. It monitors Jira and GitHub updates, pings you when PRs need approval and lets you take fast actions - all directly from Slack! Learn more →

Stats

Basic workerd repo stats
14
4,108
8.6
5 days ago
The context switching struggle is real
Zigi makes context switching a thing of the past. It monitors Jira and GitHub updates, pings you when PRs need approval and lets you take fast actions - all directly from Slack!
www.zigi.ai