We're pleased to offer our latest backend: Netlify. Netlify offers global delivery over HTTPS and HTTP/2, clever deployments, features like split-testing at the edge, and CDN-like caching, all from an engaging interface. Sound familiar? It should! That's a lot like what we do at Fly. Within this article we'll introduce Netlify then explore how it might fit together with Fly. Let's roll!
If you're hosting a static page, Netlify offers a nifty suite of tools. Similar to Heroku, your code is woven into their platform via the command line, with a simple
Apart from the benefits in static page delivery, Netlify offers a clever deployment mechanism. After connecting your GitHub repository, you can choose a deploy context and associate it with a branch. Have a particular staging branch? Deploy it and view it here. Production branch? Deploy it from the primary domain or subdomain and view it there.
Clever branch-based delivery allows Netlify to provide split-testing of different branches. Test
Controlbranch to see which vision is more effective. Simple deploys with utility and a global delivery network, those are the strengths of Netlify.
Netlify is a powerful tool. If Fly provides similar features, why provide Netlify as a backend? Modern applications are made up of much more than static sites. While many companies can launch products and provide robust experiences from static pages, if you're building a fully-featured application you'll be applying tools, services, and frameworks with more complexity.
With Fly, you can plug Netlify in as a backend for your static pages. For example, if you're building https://onehostname.com/, you can add your static Netlified marketing pages on the root domain while mounting your Heroku, Docker, Kubernetes, or self-hosted application onto
https://onehostname.com/app/. You could then add your ReadMe.io hosted documentation to
/docs/, your Amazon S3 assets to
/static/, and so on.
With Fly, your entire infrastructure receives the benefits of an intelligent global edge network, HTTP/2, HTTPS -- end-to-end encryption if Wormhole is applied -- split testing, edge Middleware, server-side page speed analytics, all from one handy control panel. Fly and Netlify may duplicate some of the goodness you receive but the result is simplicity, speed and security for everything blossoming from your hostname.
When creating a Netlify site, before you've chosen your domain and SSL strategy, you'll receive a subdomain:
https://mystaticsite.netlify.com. From within Fly, select Netlify from the list of backends, then enter that subdomain:
Click Add backend... Complete the DNS portion of the set-up if you haven't already, and then you're off to the races.
If you'd like to add Middleware, like unblockable server-side Google Analytics, the HTTPS Upgrader, and performance tracking, head-over to the Middleware tab. You can continue to add as many backends and hostnames as you'd like. Routing Rules will help you thread everything together, using HTTP Headers to keep your site secure and to bring intention to varying device or request types.
Static Pages are invaluable for creating light-weight content. Marketing pages or blogs benefit most from their splendour. Netlify offers speedy static pages through a global network, with simple and powerful deployments. The rest of your infrastructure shouldn't be left out in the cold; bringing Netlify to Fly along with the rest of your services and backends ensures that no matter what you're building, everything is served through the same global medium.
Fly started when we wondered "what would a programmable edge look like"? Developer workflows work great for infrastructure like CDNs and optimization services. You should really see for yourself, though.
Make Your Applications Fly
Faster apps, simpler tools, happier visitors.Free Signup