Cloudflare Teams Up With Open Source Community to Create New API Standards

0

Cloudflare, a security company, has announced that it is collaborating with Deno and individual core contributors of the Node.js open source project, bringing together three of the largest JavaScript environments, to give developers flexibility and choice while creating the standards of the future of edge computing. The effort will aim to ensure code developed in one environment will work in another. Any developer will be able to write and run code conforming to the set of standards–and easily transfer it–between Cloudflare Workers, Deno, and Node.js seamlessly and without the need to rewrite an application.

“Cloudflare Workers has helped to define the standard for edge computing. Since 2017, more than 450,000 developers have built on Cloudflare’s developer platform and more than three million applications have been launched,” said Matthew Prince, co-founder and CEO of Cloudflare. “But we know we’re not going to be the only one. We think that standards are important to driving the industry forward. That’s why we’re proud to be working with these other organizations in the serverless computing space to help define the standard for edge—what we believe will be the standard by which the applications of the future are developed.”

The Web-interoperable Runtimes Community Group is working with leading organizations including NearForm and Vercel to ensure that developers’ voices were heard in the creation of a new community group working within existing standards bodies. The API Standards allow developers to:

  • Use the best tool or framework for the job: It will be easier to leverage tools and integrations from the community across runtimes, allowing developers to use the best tool for the job
  • Have a uniform approach to writing server-side code: By removing platform specific nuances and the need to learn different platforms and focusing on functionality it’s easier for developers to ship better code
  • Move applications as technology needs change: As application needs evolve and change over time there is no need for massive re-writes and adding or switching vendors

Leave A Reply