From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Online hosting recommendation - VMs?
Date: Sat, 19 Aug 2017 09:41:47 +0100 [thread overview]
Message-ID: <12426883.kz2oiYslx3@dell_xps> (raw)
In-Reply-To: <05DDE068-4F38-43CD-B348-A0077AEBFFEC@stellar.eclipse.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Saturday, 19 August 2017 03:13:05 BST Stroller wrote:
> > On 18 Aug 2017, at 13:28, Todd Goodman <tsg@bonedaddy.net> wrote:
> > You'll need to look into the free tier to be sure. You can always set
> > alerts to email you if you're getting close to getting charged.
> Thanks for your help.
>
> Looks like the free tier is a bit skinny on storage - only 5GB.
>
> Linode's pricing pitch, "simple pricing, no calculator needed", puts
> Amazon's rates to shame.
>
> Stroller.
I'm going back a couple of years when I used to calculate the cost of AWS for
work purposes. The break even time of the cheapest AWS combo Vs self-hosting
of a LAMP was around 2.4 years. Now, the self-hosting was a really old and
underutilised leased corporate data centre at rather expensive prices. In
most cases the report that went back to the Board said: re-negotiate and
extend the lease of the corporate data centre for software or storage you
intend running in the long run. If you want to test some web app, then by all
means use AWS, *until* you have negotiated a better self-hosting deal. BTW,
the elastic AWS deal was almost always prohibitively expensive. The above
calculations refer to prepaying AWS for the utilisation required plus some
margin to achieve the cheapest possible deal. I appreciate that multi-year
corporate deals enjoy better discounts by suppliers than you or I walking
through the door, so YMMV.
For my current low demand needs, if I could have fibre to the premises where I
live, I would consider hosting at home and would look for a friend to provide
a hot standby and off premises back up.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-19 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 2:57 [gentoo-user] Online hosting recommendation - VMs? Stroller
2017-03-26 3:16 ` Jigme Datse Yli-RAsku
2017-03-26 12:27 ` Todd Goodman
2017-03-26 13:21 ` Alex Thorne
2017-03-28 2:08 ` [gentoo-user] " Harry Putnam
2017-03-28 2:38 ` John Runyon
2017-03-30 15:23 ` Harry Putnam
2017-03-29 12:53 ` Todd Goodman
2017-03-28 3:30 ` [gentoo-user] " J. Roeleveld
2017-03-28 3:32 ` J. Roeleveld
2017-03-28 12:41 ` Alarig Le Lay
2017-03-29 4:33 ` Stroller
2017-03-29 5:43 ` Arthur Țițeică
2017-03-29 6:09 ` Stroller
2017-08-16 22:00 ` Stroller
2017-08-17 11:40 ` Todd Goodman
2017-08-17 22:05 ` Stroller
2017-08-17 23:52 ` [gentoo-user] " Ian Zimmerman
2017-08-18 12:28 ` [gentoo-user] " Todd Goodman
2017-08-19 2:13 ` Stroller
2017-08-19 8:41 ` Mick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12426883.kz2oiYslx3@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox