* [Monitoring and Tuning the Linux Networking Stack: Receiving Data](https://blog.packagecloud.io/eng/2016/06/22/monitoring-tuning-linux-networking-stack-receiving-data/)

along with

[Monitoring and Tuning the Linux Networking Stack: Sending Data](https://blog.packagecloud.io/eng/2017/02/06/monitoring-tuning-linux-networking-stack-sending-data/)

are incredibly detailed technical posts on the networking layer within

Linux operating systems.

* [Computer networking](http://cnp3book.info.ucl.ac.be/) is a free book

that explains how networking between computer systems works. There are

also exercises for testing what you learned along the way.

* [What's the history behind 192.168.1.1? Why not 192.169.1.1 or any other IP address? When did it start being used? Who started it? Why? Why not 1.1.1.1? What is the relation to 127.0.0.1? What about 10.0.0.1 (Apple)?](https://www.quora.com/Whats-the-history-behind-192-168-1-1-Why-not-192-169-1-1-or-any-other-IP-address-When-did-it-start-being-used-Who-started-it-Why-Why-not-1-1-1-1-What-is-the-relation-to-127-0-0-1-What-about-10-0-0-1-Apple)

is a nice answer on the history of IPv4 addressing and why various

IP addresses such as 192.168.1.1 became standards for localhost or

other local networking.

* [Dropbox traffic infrastructure: Edge network](https://blogs.dropbox.com/tech/2018/10/dropbox-traffic-infrastructure-edge-network/)

explains how Dropbox uses edge-of-the-network resources closer to the

end user to optimize performance of their service.

* [Making a Reddit + Facebook Messenger Bot](https://pythontips.com/2017/04/13/making-a-reddit-facebook-messenger-bot/)

builds a bot for two platforms and shows how to deploy it to Heroku.

* [Build a Reddit bot](https://www.pythonforengineers.com/build-a-reddit-bot-part-1/)

is a four part tutorial series that starts with reading posts, continues

with

[replying to posts](https://www.pythonforengineers.com/build-a-reddit-bot-part-2-reply-to-posts/),

[automating the bot](https://www.pythonforengineers.com/build-a-reddit-bot-part-3-automate-your-bot/)

and finally

[adding behavior and a personality to the bot](https://www.pythonforengineers.com/build-marvin-the-depressed-reddit-bot-in-python/).

* [Building better bots with AWS Lex: Part 1](https://aws.amazon.com/blogs/machine-learning/building-better-bots/)

and

[part 2](https://aws.amazon.com/blogs/machine-learning/building-better-bots-part-2/)

show how to use Amazon's service offering for better natural language

processing in your bots.

* [Three challenges you’re going to face when building a chatbot](https://blog.infermedica.com/three-challenges-youre-going-to-face-when-building-a-chatbot/)

provides insightful thoughts on problems to anticipate based on the

author's experience building, deploying and scaling chatbots.

* [6 things I learned creating my own Messenger chatbot](https://kilianvalkhof.com/2017/chatbots/6-things-i-learned-creating-my-own-messenger-chatbot/)

contains some solid general advice for building your custom bots.

* [An engineer’s guide to cloud capacity planning](https://increment.com/cloud/an-engineers-guide-to-cloud-capacity-planning/)

is a wonderful article that discusses on-demand provisioning, horizontal

and vertical scaling and how to estimate performance of your infrastructure.

* [Selecting a cloud provider](https://codeascraft.com/2018/01/04/selecting-a-cloud-provider/)

reviews Etsy's decisionmaking around self-hosted infrastructure versus

cloud hosting. They put together an architectural model and ultimately

decided to start migrating over to Google Cloud Platform.

* [Going Multi-Cloud with AWS and GCP: Lessons Learned at Scale](https://metamarkets.com/2017/big-cloud-data-aws-and-gcp/)

covers the compute, networking, persistent storage, billing and

failover aspects of using more than one infrastructure provider.

* [Auth0 Architecture: Running In Multiple Cloud Providers And Regions](http://highscalability.com/blog/2018/8/27/auth0-architecture-running-in-multiple-cloud-providers-and-r.html)

explains their multi-cloud architecture and how it has evolved over the

past several years.

* [Choose A Cloud](https://www.chooseacloud.com/) has a few posts with

charts for easy cross-cloud comparisons pricing on features such as

[persistent storage](https://www.chooseacloud.com/objectstorage).

* [How Netlify migrated to a fully multi-cloud infrastructure](https://www.netlify.com/blog/2018/05/14/how-netlify-migrated-to-a-fully-multi-cloud-infrastructure/)

is another story post about developing a multi-cloud architecture and

the considerations for disaster recovery, databases and testing.

* [Ready. Steady. Go! The speed of VM creation and SSH access on AWS, DigitalOcean, Linode, Vexxhost, Google Cloud, Rackspace and Microsoft Azure](https://blog.cloud66.com/ready-steady-go-the-speed-of-vm-creation-and-ssh-key-access-on-aws-digitalocean-linode-vexxhost-google-cloud-rackspace-and-microsoft-azure/)

and

[Comparing the speed of VM creation and SSH access of cloud providers](https://blog.cloud66.com/part-2-comparing-the-speed-of-vm-creation-and-ssh-access-on-aws-digitalocean-linode-vexxhost-google-cloud-rackspace-packet-cloud-a-and-microsoft-azure/)

are one way to measure some of the infrastructure speed provided by several

cloud vendors. The virtual machine and SSH access data points are taken in

multiple regions. It's unclear how these metrics would change over time based

on backend tweaks made by each provider.

* The [State of Cloud Instance Provisioning](https://ahmet.im/blog/cloud-instance-provisioning/)

explains the tools and operations behind how AWS,

[DigitalOcean](/digitalocean.html), Google Cloud and Microsoft Azure stand up

virtual machine instances for you to use.

* [VPS $5 Showdown - October 2018 - DigitalOcean vs. Lightsail vs. Linode vs. Vultr](https://joshtronic.com/2018/10/15/vps-showdown-october-2018/)

compares and contrasts the cheapest options for four popular virtual

private server providers.

* [VPS comparisons](https://github.com/joedicastro/vps-comparison) uses

[Ansible](/ansible.html) to get some data around provisioning speed

and system performance. The whole

[README](https://github.com/joedicastro/vps-comparison/blob/master/README.org)

file in that repository has a ton of useful information and summaries

of the tested providers.

title: Containers

category: page

slug: containers

sortorder: 0535

toc: False

sidebartitle: Containers

meta: Containers are a concept where processes are run isolated on a operating system.

<h3>What do you want to learn next about web development?</h3>

<div class="row">

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/continuous-integration.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/monitoring.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/logging.html" %}

</div>

</div>

<h3>What's next after setting up macOS?.</h3>

<div class="row">

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/application-dependencies.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/web-servers.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/django.html" %}

</div>

</div>

<h3>What's next after setting up macOS?.</h3>

<div class="row">

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/application-dependencies.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/web-servers.html" %}

</div>

</div>

<div class="c4">

<div class="well select-next">

{% include "choices/buttons/django.html" %}

</div>

</div>