I just hope the draft as-is expires and never makes it to an RFC.
1,108 karma · joined August 9, 2010
I just hope the draft as-is expires and never makes it to an RFC.
Thanks :) !
Is the subheading "Spin up Instant Varnish Nodes for ..." not descriptive enough of the service? Perhaps I'm better off writing a short paragraph right before the "features" section?
Now that I've read your comment and sogen's, it's pretty clear I need a quick explainer of both the service and Varnish. Perhaps I need to fuse both into a paragraph.
Much appreciated!
People who can do this serially are never out of work.
By the way, and I'm going out on a limb with my shameful plug, I built a Varnish-as-a-Service kind of infrastructure called Cachoid ( https://www.cachoid.com ). But to my own defense, I'm putting my energy, time, and money where my mouth is.
Yes, that's the plan in consideration. I'll get in touch should that pan out.
I also recall being confused as to how this will work with an on-premise IaaS type app. For example, I'm gauging interest for shipping "Cachoid" to service providers so they can offer it to their end users. And this is where I think Keygen could help. What kind of pricing are you considering so far?
Thanks
I'm bootstrapped so I'm grateful in advance for feedback, comments, things I need to improve, and things you need to see before you seriously consider using something like this.
Outline:
0. Instant Varnish Cache nodes (< 10s) with ready-to-go VCLs you can spin from an increasing number of locations; each node runs inside its own container
1. Four 21-days trials. To hell with credit cards!
2. Simple API endpoint to get page cache status, push new VCLs, purge, upload TLS/SSL certificates, push HTML files (Varnish hosted).
3. ModSecurity rules a click away
4. WordPress, AWS S3, Github.io, and file/static hosting (HTML-uploaded files cached inside your Varnish instance) VCLs. So Cachoid will memory-cache your "backends" and serve them like hot pancakes
5. E2EE is a few clicks away if you have an TLS/SSL cert. It's rough around the edges but works
6. Internal & external monitoring of nodes
7. Google 2FA to access your Cachoid account
8. Stripe subscription, one-time Paypal & Stripe, Bitcoin (through Stripe)
9. Other features I haven't listed that I feel would make me sound like a car salesman like load balancing and auto resource upgrade (I almost tricked you there, see?)
10. Check out this page if you're curious. It has screen shots and articles: https://www.cachoid.com/support
Some uses cases:
1. Survive the hug of death (HN, Reddit, etc) with high flying colors
2. Cache static sites, S3 "sites", github.io, etc. Smooth out the sporadic speed issues
3. Cache CMS sites like WordPress
4. Cache certain API endpoints
As for the technical part, I think you're better off passing a callback URL to the service so it posts to it when the user verifies the email. The callback URL could be an AWS lambda.
Good luck!
I bet the "cold war" mind set works the same way. You rarely see cold war brought up by much younger folks. It's always an old gen rehash.
What about a ruthless dictator like Kim Jong Un getting 12 extra years on earth?
I think the trough is more mentally manageable this way.
You probably meant to say utmost. Outmost could imply a lesser importance or the complete opposite if read into too much.
Anyway, I'm looking forward to testing it out and integrating v5 with Cachoid ( shameful plug: https://www.cachoid.com/ ).