CoreOS on Google Compute Engine (and how to scale Wordpress in 5 minutes).
CoreOS on Google
and how to scale Wordpress in 5 minutes.
Google Compute Engine (GCE)
“Google Compute Engine is a service that provides virtual
machines that run on Google infrastructure. Google
Compute Engine offers scale, performance, and value that
allows you to easily launch large compute clusters on
Google's infrastructure. There are no upfront investments
and you can run up to thousands of virtual CPUs on a
system that has been designed from the ground up to be
fast, and to offer strong consistency of performance.”
GCE vs AWS
Pricing & sub-hour billing
Load Balancer needs no pre-warming
Persistent Disks that can be connected to multiple VMs
Better Block Storage (10TB which is 10 times , include i/o pricing no more guessing)
Integrated networking (vpn, public subnets, firewalls, routes, gateway, ACL, part of gce
6. Better network throughput (AWS uses public Internet for communicating between the
regions . GCE much faster, uses google infrastructure).
7. Multi-Region images (all images are global unlike aws, which needs explicit)
8. Persistent IP addresses (no need to reassociate after each stop/start of VM)
9. Faster boot times & auto restart of VMs (5X faster than Amazon EC2, 30
seconds for first login)
Live migration (graceful live migration of VMs from one host to another making it transparent)
Minimal: Linux kernel + systemd
Simple: Package manager is Docker
Secure: Auto-updates & read-only fs
Clustered: Distributed automatically and fails
over seamlessly thanks to etcd and systemd.
● Never gonna give you up
tl;dr: CoreOS is cool
You get a stable host dedicated to running
docker instances, and nothing else.
It’s never gonna:
● give you up
● let you down
● run around and desert you
WTF is etcd?
open-source HTTP distributed key value store
sure, but why??
so that your apps can use it to store:
● database connection details
● cache settings
● feature flags
● and more
Cool etcd features
Simple, curl-able API (HTTP + JSON)
Optional SSL client cert authentication
Benchmarked 1000s of writes/s per instance
Properly distributed using Raft protocol
Keys support TTL
Atomic test and set
Easily listen for changes to a prefix via HTTP