new paas and redis resources

mattmakai · mattmakai · commit 0a9cf1b1d607 · 2018-11-29T07:42:07.000-05:00
diff --git a/content/pages/03-data/11-redis.markdown b/content/pages/03-data/11-redis.markdown
@@ -13,7 +13,7 @@ database typically classified as a [NoSQL database](/no-sql-datastore.html).
 Redis is commonly used for [caching](/caching.html), transient data storage
 and as a holding area for data during analysis in Python applications.
 
-<a href="https://redis.io/" style="border: none;"><img src="/img/logos/redis.jpg" width="100%" alt="Redis logo." class="technical-diagram" /></a>
+<a href="https://redis.io/" style="border: none;"><img src="/img/logos/redis.jpg" width="100%" alt="Redis logo." class="shot" /></a>
 
 <div class="well see-also">Redis is an implementation of the <a href="/no-sql-datastore.html">NoSQL database</a> concept. Learn more in the <a href="/data.html">data</a> chapter or view the <a href="/table-of-contents.html">table of contents</a> for all topics.</div> 
 
@@ -136,3 +136,8 @@ get started in those areas.
 * [A Speed Guide To Redis Lua Scripting](https://www.compose.com/articles/a-quick-guide-to-redis-lua-scripting/)
   shows how to use the Lua programming language to create extensions
   for Redis.
+
+* [Better tests for Redis integrations with redislite](https://www.obeythetestinggoat.com/better-tests-for-redis-integrations-with-redislite.html)
+  shows how to mock out a Redis instance using the 
+  [redislite](https://github.com/yahoo/redislite) library and clean up
+  existing hacks you may be using to test your Redis usage.
diff --git a/content/pages/04-web-development/35-testing.markdown b/content/pages/04-web-development/35-testing.markdown
@@ -176,3 +176,8 @@ use mocks in your test cases.
   [Redis](/redis.html)-dependent code but prefer to mock it rather than
   ensure an installation and connection are present whenever you run
   your tests.
+
+* [Better tests for Redis integrations with redislite](https://www.obeythetestinggoat.com/better-tests-for-redis-integrations-with-redislite.html)
+  is a great example of how using the right mocking library can clean
+  up existing hacky testing code and make it more straightforward for
+  any developer that happens upon the tests in the future.
diff --git a/content/pages/05-deployment/09-paas.markdown b/content/pages/05-deployment/09-paas.markdown
@@ -57,12 +57,40 @@ application framework and your app itself is up to date and secured. See the
 
 * [OpenShift](https://openshift.redhat.com/community/get-started/python)
 
-* [AWS Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/),
-  [AWS CodeStar](https://aws.amazon.com/codestar/)
+* [AWS Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/) and
+  [AWS CodeStar](https://aws.amazon.com/codestar/) are Amazon Web Services'
+  PaaS offerings. CodeStar is the newer service and recommended for new
+  projects.
+
+
+## Platform-as-a-service open source projects
+The following open source projects allow you to host your own version
+of a platform-as-a-service. Running one of these gives you the advantage
+of controlling and modifying the project for your own applications,
+but prevents you from offloading the responsibility of keeping servers
+running to someone else.
+
+* [Kel](http://www.kelproject.com/) uses Kubernetes as a foundation
+  for a custom self-hosted PaaS. Note that it was created by Eldarion,
+  which had one of the first Python-specific PaaS offerings on the
+  market around the time that Heroku was launched.
+
+* [Dokku](http://dokku.viewdocs.io/dokku/) builds on Docker and has
+  hooks for plugins to extend the small core of the project and customize 
+  deployments for your applications.
+
+* [Convox Rack](https://github.com/convox/rack) is open source PaaS
+  designed to run on top of AWS services.
+
 
 
 ## Platform-as-a-service resources
-* [PaaS bakeoff: Comparing Stackato, OpenShift, Dotcloud and Heroku for Django hosting and deployment](http://appsembler.com/blog/paas-bakeoff-comparing-stackato-openshift-dotcloud-and-heroku-for-django-hosting-and-deployment/) by [Nate Aune](https://twitter.com/natea).
+* [The differences between IaaS, PaaS and SaaS](https://www.engineyard.com/blog/the-differences-between-iaas-paas-and-saas-and-when-to-use-each)
+  explains the abstract layer differences among "X-as-a-service" offering
+  types and when to consider using each one.
+
+* [PaaS bakeoff: Comparing Stackato, OpenShift, Dotcloud and Heroku for Django hosting and deployment](http://appsembler.com/blog/paas-bakeoff-comparing-stackato-openshift-dotcloud-and-heroku-for-django-hosting-and-deployment/) 
+  by [Nate Aune](https://twitter.com/natea).
 
 * [Deploying Django](http://www.rdegges.com/deploying-django/) by 
   Randall Degges is another great free resource about Heroku.
@@ -72,6 +100,10 @@ application framework and your app itself is up to date and secured. See the
   currently called and what they could've been called to be more 
   clear to users.
 
+* [PAAS comparison - Dokku vs Flynn vs Deis vs Kubernetes vs Docker Swarm in 2017](http://www.jancarloviray.com/blog/paas-comparison-2017-dokku-flynn-deis-kubernetes-docker-swarm/)
+  covers high-level advantages and disadvantages of several self-hosted PaaS 
+  projects.
+
 * [5 AWS mistakes you should avoid](https://cloudonaut.io/5-aws-mistakes-you-should-avoid/)
   explains how common beginner practices such as manually managing 
   infrastructure, not using scaling groups and underutilizing instances can 
@@ -125,6 +157,11 @@ application framework and your app itself is up to date and secured. See the
   on Google Cloud and posits what they may be paying to run their
   service.
 
+* [PaaS (false) economics](https://blog.drie.co/paas-false-economics-13f72d87b485)
+  gives some quick back-of-the-envelope calculations on why running your
+  applications on a PaaS is obviously going to appear more expensive if you 
+  do not take the cost of your own software engineers into the equation.
+
 * Two blog posts on using AWS Autoscaling in [Automatic replacement of Autoscaling nodes with equivalent spot instances](https://mcristi.wordpress.com/2016/04/21/my-approach-at-making-aws-ec2-affordable-automatic-replacement-of-autoscaling-nodes-with-equivalent-spot-instances/)
   and
   [Autoscaling nodes: seeing it in action](https://mcristi.wordpress.com/2016/04/27/automatic-replacement-of-autoscaling-nodes-with-equivalent-spot-instances-seeing-it-in-action/)
diff --git a/content/pages/meta/00-change-log.markdown b/content/pages/meta/00-change-log.markdown
@@ -16,7 +16,8 @@ on GitHub.
 
 ## 2018
 ### November
-* Updated the [logging](/logging.html) page with a bunch of new resources.
+* Updated the [logging](/logging.html), [Redis](/redis.html) and
+  [PaaS](/platform-as-a-service.html) pages with a bunch of new resources.
 * Updated the [web design](/web-design.html) page with new resources.
 * Updated the [data visualization](/data-visualization.html) page with
   new resources.
