Or if you want to go old school, cheaper, and less sexy/api driven: https://www.delimiter.com/
If you shop, for around 30-40 a month you can get 16 cores, 32gb ram, and a 120GB ssd or 1-2TB spinny disk.
Or if you want to go old school, cheaper, and less sexy/api driven: https://www.delimiter.com/
If you shop, for around 30-40 a month you can get 16 cores, 32gb ram, and a 120GB ssd or 1-2TB spinny disk.
I can't stress this enough. Having to roll your own / administrate a logging system, Database, load balancers, autoscale, file storage far exceeds the added cost of the cloud. Now that GCE has sustained usage discounts of 39% it makes no sense to go bare metal right now.
Packet - $292/mo
4 cores
32 GB memory
128 GB SSD
Google Compute Engine - $176/mo
$156 - custom-4-32-extended
4 cores / 32 GB memory
$20 - 120 GB SSD storagehttps://cloud.google.com/compute/docs/machine-types
> For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), 2.2 GHz Intel Xeon E5 v4 (Broadwell), or 2.0 GHz Intel Skylake (Skylake).
I'd have one (or more) already if I didn't live on the opposite side of the world to the data center.
IMO, docker and container orchestration spells a bright future for bare-metal boxes like these, as you won't need cloudformation, etc..
But I still see few alternatives to S3, many vendors offers block devices, but only the big clouds offer blob storage. Backup and restore from blob storage makes recovery from crash pretty easy.
The not-my-problem aspect is really powerful.
I would be concerned with how good the connection is... Ie. if you use packet or scaleway, how stable/fast is the connection to b2.
S3 being internal network at EC2 is a killer feature too :)
There has to be something that adds more bare-metal for your docker containers to run on when the existing bare-metal reaches capacity, right?
K8s is getting pretty easy to setup these days.
Cloudformation, to me at least, is the power to expand resources for large traffic events. Most of the time you can get by with a small amount of instances but its nice when it scales up to hundreds of instances in minutes.
The bare metal equivalent would be to buy something that can handle the peak load from the start, right?
This is not what CloudFormation does. CloudFormation allows a declarative way to express a group of AWS resources to be created and coupled together. There's nothing that's quite exactly the same as CloudFormation, but stock Kubernetes is quite close, since you effectively describe what resources you want in individual declarative YAML/JSON files. However, there's nothing standard in Kubernetes for coupling them together into one thing equivalent to a Stack in CloudFormation.
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuid...
Note: I'm still hopeful that things like k8n will make running stateful containers on random metal easy without huge investments in configuration for backup and reliability.
I pay about $3.50/mo total to run these services.
$50/month 24GB ram, 16 threads, 2TB HD, gigabit uplink (20TB/month free).
It's not hard to wait until they have a sale and/or coupons and/or pay upfront yearly to get a similar config for 30-40.
(disclaimer: these servers are pretty "unmanaged")
Or packet gives you a completely "cloud/api-driven" experience that's still on bare metal and reasonably priced compared to AWS or DO.
What is that $70/mo server with 16 cores?
The cheapest I see is Kimsufi KS-5 8-core for $36/month. There's also an EU hoster Netcup that offers RS 4000 8-core for around $33.