Cms 140 static web content

docs/use-cases/.pages

@@ -1,2 +1,3 @@
 nav:
     - index.md
+    - static-web-content.md

docs/use-cases/static-web-content.md

@@ -0,0 +1,33 @@
+# I have Ceph.  So now what?  Application notes for Ceph cluster usage.
+
+Ceph has three primary client interfaces available: RGW, an Amazon S3
+compatible web interface; RBD, a block interface the behaves like a
+network attached disk drive; and CephFS, and network filesystem.
+
+Once a new Ceph cluster has been created, it wants to hold your data.
+Let’s explore some of these.  First up is the S3 compatible RADOS
+Gateway interface, or RGW.
+
+Being S3 compatible, RGW can be used for anything Amazon’s S3 storage
+is used for.  One use great fit for RGW is serving static web objects:
+
+- CSS files
+- Javascript library files
+- Images and videos
+- Binary files meant for download
+- PDF documents
+
+In a typical deployment, the contents of these files are not changed
+by the web server before being sent to the client.  RGW does not have a
+template engine like PHP built in, so little configuration is needed to
+have RGW serve the content to client browsers.
+
+Ceph itself uses excellent data integrity mechanisms to ensure that your
+content does not suffer from unnoticed corruption.  What clients read
+back will always match what was originally stored.
+
+Additionally, RGW can replicate data from one Ceph cluster to another.
+This can be used in a hub and spoke deployment to distribute web objects
+across geographies, improving client access latencies.  And can also be
+used as an automatic backup mechanism to avoid outages.
+