ruben_varnish
Technical Summary:
* In-Core TLS: Termination is handled natively by the engine process. No sidecars required.
* K8s Gateway API: Full implementation. Routing is defined via standard Kubernetes resources. Code here: https://github.com/varnish/gateway
* No VCL: A new Rust routing engine ("Ghost") handles dynamic traffic. VCL is not required for standard routing.
* Observability: Native OpenTelemetry/Prometheus exporters and structured JSON logs.
Home of our downstream distribution: https://varnish.org
Leaning towards making the modules/examples permissive, indeed.
Do you think the whole MACH stack users would then move their workload to such a controller/ingress/gateway?
I think they wouldn't, because they don't necessarily understand (or need?) the advantages of caching at scale and flexibility that Varnish provides.
But if you say that you will accelerate everything in their K8s cluster... Then maybe ;)
We'll see. I have a wish for Kubecon in Q4
But yes, Varnish Cache is not exactly what you would call Cloud Native.
Varnish Software have launched Pro currently on AWS only at a much lower price point, but it is still somewhat limited. I think that a Free-tier providing some of the goodies you mention would also cover much of what's needed for today's workloads including better memory management, in-core TLS and a better developer experience by having much better K8s support. Much of this could and should go into Varnish Cache, but that is a longer road as the project as such has a different focus than we do.
Expect more on that front this year @pbower :)
Would you have read this if neither Deno, Varnish or TinyKVM would have been in the title? ;)
But we hear you. Will put a page on our website and should probably consider seeing up a community site as well as it is indeed, grabbing some attention.
Tip, Although not entirely what you asked, but related: what about using more caving in your CI/CD Pipeline. Customers see incredible time savings when using Varnish on that context (mostly with Enterprise w/MSE4 as you will need a massive cache, but it can be useful even with Varnish Cache grounding on your pipeline and workflow). If you are interested, read more here: https://www.varnish-software.com/solutions/data-ai-accelerat...
Could you specify this a bit? @codethief
The way it's phrased makes it sound like you want to stuff TinyKVM into a container, but I suspect what you are actually asking to implement an OCI runtime with TinyKVM https://github.com/opencontainers/runtime-spec/blob/main/spe...
Does that make more sense?
You can find a bunch of posts related to this topic there as well.
That? Works like a charm.
It's available with the on-premise enterprise subscription and on the AWS and Azure clouds as Varnish Plus - Caching Engine:
https://aws.amazon.com/marketplace/seller-profile?id=263c020...
https://azuremarketplace.microsoft.com/en-us/marketplace/app...
I have personally learned so much from that experience that it is very difficult to overlook when thinking of brand hacks.
Then I ask them to try the same with their Apple laptop.
That normally makes them never ask such questions again.
I learned that from an IBM (and later a Lenovo) sales person when presenting the X series. It's designed and built to tolerate real use. And some abuse :-)
EVERY single thing has worked with Ubuntu (every single six months release, since 12.04 only used LTS releases) and required little to no effort.
As for a "Desktop" I haven't touched one at work since 2004. TBH I believe only gamers care. And gamers like to build/adapt their own hardware. Unless you can differentiate heavily and have something unique (something like building a RED camera or a super fast Electrical car) how is that going to fly in a marked that is in decline?
Keep yourselves to building a super high end laptop that can rival a Lenovo X series model and we will look into that.
As Lasse pointed out, we never meant to take away any merit from your work. If you feel we could highlight the Hitch's origin from Stud better, let us know how. We are open to suggestions.
And yes, if you ever come to Oslo, you have an open invitation to come by an test our homebrew :)
I believe that the power and utility of VSL are so underestimated and overlooked that I don't know where to start...
If you make your own VMOD(can take from a few hours to days), make sure to send a PR and add it to the directory above (IOW: share it) :)
Made by Varnish Software to provide a "browser-vendor-compliant" HTTP/2 stack.
Varnish Cache 5.0
You can get it here: https://github.com/varnish/hitch Read more about it here: https://hitch-tls.org/
Stud No More. Enter Hitch from Varnish Software
10 years of Varnish Cache
* Upgrading notes: https://www.varnish-cache.org/docs/4.0/whats-new/upgrading.h...
* A script by Fed that will do 70-90% of the job for you: https://github.com/fgsch/varnish3to4
Let us know how it went :-)
Obviously, depending on what you were trying to do and to which extend Varnish was extendable then (VMODs were added in 3.0) it might not have been the best option there is.
Anyway, thank you for your reply. It was a very interesting insight you came with there.
* https://github.com/mattiasgeniar/varnish-3.0-configuration-t... (fairly well maintained with CMS specific VCL examples)
* https://github.com/slashsBin/nuCache (library for different programming languages, not so CMS centric)
Both of these are listed in our utilities directory:
* https://www.varnish-cache.org/utilities
Other Varnish (VCL) extensions can be found in the VMOD directory:
* https://www.varnish-cache.org/vmods
If you have ideas on how to make both these resource more visible and accessible for our users, please let me know.
Your own caching will make your webapp (or API) scale (say 2x faster or serve 15x the amount of users), but if you need your app to take some serious beating (say 100x to 400x the amount of users with minimal ttfb) because your site/app suddenly becomes flavour of the month on the Internet, then you will really need Varnish.
After seeing several Paywall and API deployments and all sorts of other advanced business logic, such as GeoIP detection or Mobile device classification, applied in the cache layer while keeping a sane and simple VCL, I am not sure your initial point is the case. The normal way to write VCL is to keep it simple.
(Yes, I am biased, but my point is still valid).
[Varnish Software sales hat on]