7. Base Services Add-ons
DNS
Email
Full-text Search
Routing
Mesh Perf Mgmt
Shared DB
Dyno
Grid
DB
Worker
Grid Memcached
Deploy Developer API Partner
Tools CLI Web API
15. PING google.com (66.102.7.99): 56 data bytes
64 bytes from 66.102.7.99: icmp_seq=0 ttl=54 time=27.002 ms
64 bytes from 66.102.7.99: icmp_seq=1 ttl=54 time=36.446 ms
64 bytes from 66.102.7.99: icmp_seq=2 ttl=54 time=25.828 ms
PING pingtest.net (69.17.117.207): 56 data bytes
64 bytes from 69.17.117.207: icmp_seq=0 ttl=48 time=71.158 ms
64 bytes from 69.17.117.207: icmp_seq=1 ttl=48 time=72.828 ms
64 bytes from 69.17.117.207: icmp_seq=2 ttl=48 time=89.200 ms
16. PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data.
64 bytes from 2.2.2.2: icmp_seq=1 ttl=61 time=0.436 ms
64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms
64 bytes from 2.2.2.2: icmp_seq=3 ttl=61 time=0.548 ms
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=1.94 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=1.90 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=2.01 ms
18. PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data.
64 bytes from 2.2.2.2: icmp_seq=1 ttl=61 time=0.436 ms
64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms
64 bytes from 2.2.2.2: icmp_seq=3 ttl=61 time=0.548 ms
PING 192.168.1.7 (192.168.1.7): 56 data bytes
64 bytes from 192.168.1.7: icmp_seq=0 ttl=64 time=1.111 ms
64 bytes from 192.168.1.7: icmp_seq=1 ttl=64 time=0.574 ms
64 bytes from 192.168.1.7: icmp_seq=2 ttl=64 time=0.553 ms
our values are machette
this preso about our values, and how that drove our architecture and some ideas on combining our values with the changes happening in cloud
Today this seems obvious, but at the start it was crazy talk. Starting with values of incredibly tight workflow meant git, lead to this crazy idea with git
we addressed this by splitting everything into it’s own component. And when we did that, we realized that that pattern opens up the ability for anyone else to provide a component as well
FFMPEG ami.
Went after the simple angle.
New Bamboo put together an ami providing fully curated stack
monetization strategy too.
Too be fair, this is a model that’s been around for years. There is a new change though.