@@ -5866,6 +5866,11 @@ <h2>Docker resources</h2>
58665866 well worth buying.</ p >
58675867</ li >
58685868< li >
5869+ < p > < a href ="https://github.com/odewahn/docker-jumpstart/ "> Docker Jumpstart</ a > is a
5870+ comprehensive introduction to what Docker is and how to get started with
5871+ using the tool.</ p >
5872+ </ li >
5873+ < li >
58695874< p > < a href ="http://pythonforengineers.com/what-the-bleep-is-docker/ "> What the Bleep is Docker?</ a >
58705875 is a plain English explanation with examples of what Docker provides and
58715876 what it can be used for in your environment.</ p >
@@ -5919,7 +5924,6 @@ <h2>Python-specific Docker resources</h2>
59195924 from the perspective of Python developers handling deployments.</ p >
59205925</ li >
59215926</ ul >
5922- < h3 > What do you want to learn next about deployment?</ h3 >
59235927 < h1 > Caching</ h1 >
59245928< p > Caching can reduce the load on servers by storing the results of common
59255929operations and serving the precomputed answers to clients. </ p >
@@ -5956,19 +5960,23 @@ <h2>Caching resources</h2>
59565960</ li >
59575961</ ul >
59585962< h2 > Caching learning checklist</ h2 >
5959- < p > < i class ="fa fa-check-square-o "> </ i >
5960- Analyze your web application for the slowest parts. It's likely there are
5961- complex database queries that can be precomputed and stored in an in-memory
5962- data store.</ p >
5963- < p > < i class ="fa fa-check-square-o "> </ i >
5964- Leverage your existing in-memory data store already used for session data
5965- to cache the results of those complex database queries.
5966- A < a href ="/task-queues.html "> task queue</ a > can often be used to precompute the results
5967- on a regular basis and save them in the data store.</ p >
5968- < p > < i class ="fa fa-check-square-o "> </ i >
5969- Incorporate a cache invalidation scheme so the precomputed results remain
5970- accurate when served up to the user.</ p >
5971- < h3 > What do you want to learn now that your app is responding faster?</ h3 >
5963+ < ol >
5964+ < li >
5965+ < p > Analyze your web application for the slowest parts. It's likely there are
5966+ complex database queries that can be precomputed and stored in an in-memory
5967+ data store.</ p >
5968+ </ li >
5969+ < li >
5970+ < p > Leverage your existing in-memory data store already used for session data
5971+ to cache the results of those complex database queries. A
5972+ < a href ="/task-queues.html "> task queue</ a > can often be used to precompute the results
5973+ on a regular basis and save them in the data store.</ p >
5974+ </ li >
5975+ < li >
5976+ < p > Incorporate a cache invalidation scheme so the precomputed results remain
5977+ accurate when served up to the user.</ p >
5978+ </ li >
5979+ </ ol >
59725980 < h1 > Code Metrics</ h1 >
59735981< p > Code metrics can be produced by static code analysis tools to determine
59745982complexity and non-standard practices.</ p >
@@ -6055,6 +6063,15 @@ <h1>Change Log</h1>
60556063the
60566064< a href ="https://github.com/makaimc/fullstackpython.github.com/commits/gh-pages "> source repository's commit log</ a > on GitHub.</ p >
60576065< h2 > 2015</ h2 >
6066+ < h3 > June</ h3 >
6067+ < ul >
6068+ < li > Added new < a href ="/docker.html "> Docker</ a > resources.</ li >
6069+ < li > Made some changes to what is contained in the Markdown files versus the
6070+ HTML Jinja2 templates. Behind the scenes work that needed to be done to
6071+ move the project forward.</ li >
6072+ < li > Work continues on the
6073+ < a href ="http://www.deploypython.com/ "> Full Stack Python Guide to Deployments</ a > book.</ li >
6074+ </ ul >
60586075< h3 > May</ h3 >
60596076< ul >
60606077< li > Got a whole lot of work done on my upcoming
0 commit comments