4 ms·
via https://twitter.com/justincormack/status/1119217911380545536 https://twitter.com/justincormack/status/1119217911380545536 interesting to see some technical
by moderation 7y ago
via https://twitter.com/justincormack/status/1119217911380545536 https://twitter.com/justincormack/status/1119217911380545536 interesting to see some technical detail in the S1 including a likely reference to WASM, WASI and Lucet [0].
"Moreover, our platform is highly technical and complex and relies on the Varnish Configuration Language (VCL). Potential developers may be unfamiliar or opposed to working with VCL and therefore decide to not adopt our platform, which may harm our business."
"We will continue to work on open source projects, which will empower developers to build applications in multiple languages, and run them faster and more securely at our edge"
[0] https://github.com/fastly/lucet/ https://github.com/fastly/lucet/
- slivanes 7y agoI was tasked to integrate Fastly into our infrastructure having not done any configuration with Varnish (VCL) before. ~10k req/s VCL can be challenging for complex flow control (IMO), but it is made easier with Fastly enhanced/custom VCL modules. Their documentation was good, and the Fastly support team was excellent. Their sales engineers gave us a baseline configuration that suited our needs and were quick to answer any followup questions. Haven't noticed any downtime or response delays to date.
- greenleafjacob 7y agoCheck out this flow diagram for Varnish 2 [1]. [1] http://www.kalenyuk.com.ua/wp-content/uploads/2009/12/varnish-2.0.4-flow.jpg http://www.kalenyuk.com.ua/wp-content/uploads/2009/12/varnis...