You need a couple of miracles to get people to listen. And you need true prophecies (accurate predictions of the future) to have long term following.
Good luck
1,108 karma · joined August 9, 2010
You need a couple of miracles to get people to listen. And you need true prophecies (accurate predictions of the future) to have long term following.
Good luck
We host (the fully managed kind) several clients' projects (small and medium). It isn't atypical to have some clients hire us for server "management" as insurance. Meaning we only dive in when something awry happens to their stack and they need that jack-of-all-trade tech who can pinpoint the culprit quickly. ~$30/mo as insurance is peanuts compared to potential revenue gaps.
Others want a turnkey solution where we document the details of their stack and we manage the ops part in coordination with the dev. I think this is where the most value is captured by our clients.
There are other interesting outlier cases but it's likely OT :)
A setup that works for a certain service won't necessarily work for another unless yours is a very close replica. Based on my experience in this area, and I'm a performance seeking nut, each platform, and even each traffic pattern, needs its own thinking hat.
That's what makes it so fun!
We manage servers for client with a similar requirement but it rarely exceeds $250/mo for several TBs plus the cost of a consumer CDN.
I feel (I don't have direct experience with this setup) like they're just offloading some compute power (therefore cost) to the hosts. So the cost is automatically spread out across their relatively massive edge nodes. A line showing a router plus support costing $100,000 looks bad in expenditures vs showing a server plus integrated routing showing $2500.
I'm curious about how this impacts Varnish considering how table look ups can be bus-expensive during odd route changes/flaps (storms). %sys must go through the roof as a result.
Yes I can see how goofy mine would read. It's one of those things I'd be embarrassed of about a week or two later. But writing one's own copy is much more personal especially when it's a story.
I understand boot up completes in under a second but if one needs to setup an environment to do something useful, it can take several seconds. I guess what I'm getting at is why would the fast boot matter when one still needs to setup a basic environment to complete a task?
This is analogous to achieving an artificially low TTFB but actual rendering doesn't start until several seconds later.
Am I missing something?
Thanks
Sadly, it isn't always possible.
"I also think there's a lot of potential for premium or subscription or even user-paid content. Some sort of paywall or membership."
It's unfair IMO.
Most small software companies have a single entity and only choose to spin out when a new product becomes a truly independent operational unit, when it receives investment, or (for branding purposes) if it ends up eating the business that spawned it.
Is there any legal ramification to "converting" product X, originally under the umbrella of Y LLC, to its own new X LLC?
Thanks
1) Timezone of server is set to one other than the geographical location's
2) Gzip-compressed page or asset is cached. Therefore the embedded date/time is from an unknown past.
So this reduces the good guesses a bit.
But now I'm going to miss out on text because I'm done skimming and it hasn't appeared yet.
It looks like you're making its application so broad that you're hurting your chances. Unless you pick one problem, that exists right now, to solve I'm suspecting this isn't going to be a hit.
The monthly compute price is $0.00001667 per GB-s and the free tier provides 400,000 GB-s.
Total compute (seconds) = 3M (1s) = 3,000,000 seconds # ( roughly equals to 8640 * 300 ~ 2.6M seconds in the case of this app)
Total compute (GB-s) = 3,000,000 * 512MB/1024 = 1,500,000 GB-s
Total compute – Free tier compute = Monthly billable compute GB- s
1,500,000 GB-s – 400,000 free tier GB-s = 1,100,000 GB-s
Monthly compute charges = 1,100,000 * $0.00001667 = $18.34
Have you completely abandoned the traditional methods?
To ensure that your servers are kept in a cached state, you can manually configure a scheduled task for your Zappa function that'll keep the server cached by calling it every 5 minutes.
The cost of running the warmer (300s * ~3M * 512MB) comes out to about $18 and that's not counting the number of actual requests from end users. It's interesting but costly as a substitute.
What do people always need?
* Drinking water
* Food
* Health
* Shelter
Pick one or two.