Writing an API at the Edge with Workers and Cloud Firestore
We’re super stoked about bringing you Workers.dev, and we’re even more stoked at every opportunity we have to dogfood Workers. Using what we create keeps us tuned in to the developer experience, which takes a good deal of guesswork out of drawing our roadmaps.
Our goal with Workers.dev is to provide a way to deploy JavaScript code to our network of 165 data centers without requiring developers to register a domain with Cloudflare first. While we gear up for general availability, we wanted to provide users an opportunity to reserve their favorite subdomain in a fair and consistent way, so we built a system to allow visitors to reserve a subdomain where their Workers will live once Workers.dev is released. This is the story of how we wrote the system backing that submission process.
Requirements
Of course, we always want to use the best tool for the job, so designing the Workers that would back Workers.dev started with an inventory of constraints and user experience expectations:
Constraints
- We want to limit reservations to one per email address. It’s no fun if someone writes a bot to claim every good Workers subdomain in ten seconds; they Continue reading
Schrödinger’s cat or stone soup, pick your favorite ONAP analogy.
The electrical contractor and technology integrator deployed a Silver Peak-based managed SD-WAN...
In this podcast, you will hear O2/ Telefonica, Cardinality and Dell EMC as they jointly showcase...
The storage vendor isn’t aware of any customer attacks resulting from the vulnerability and said...
The new project, DataProjects.org, will offer coursework for improving data literacy and has a...
The 5G race heats up in Ireland as all three operators plan to launch services in 2019. Huawei...