diff --git a/CHANGES.md b/CHANGES.md
index cc941e0..0079e1b 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -3,6 +3,7 @@
 #### New Docs
 
   - added [a new FAQ entry](/docs/FAQs/PollADatabaseEvery60.md) How do I turn on/off polling a database every 60 secs  (hint: effects)
+  - added [a new FAQ entry](/docs/FAQs/FullStackReframe.md) How do I do full-stack re-frame?
 
 ## 0.10.1  (2017.08.17)
 
diff --git a/docs/FAQs/FullStackReframe.md b/docs/FAQs/FullStackReframe.md
new file mode 100644
index 0000000..d844120
--- /dev/null
+++ b/docs/FAQs/FullStackReframe.md
@@ -0,0 +1,20 @@
+### Question
+
+I'm interested in taking the re-frame concepts and applying them to 
+my entire Client/Server stack.  
+
+### Short Answer
+
+You'll want to investigate CQRS (vs REST).
+
+### Notes
+
+1. Perhaps watch [Bobby Calderwood's video](https://www.youtube.com/watch?v=B1-gS0oEtYc)
+2. Look at his [reference implmentation](https://github.com/capitalone/cqrs-manager-for-distributed-reactive-services) or [this alternative](https://github.com/greywolve/calderwood)
+4. Be aware that "Event Sourcing" often comes along for the ride
+   with CQRS, but it doesn't have to. It adds complexity (Kafka?). 
+   Don't do it lightly. Maybe just use CQRS without ES? 
+5. If you do want Event Sourcing, then Kafka might be your friend
+   and Greg Young might be your God.  [Onyx](https://github.com/onyx-platform/onyx) might also be interesting to you.
+
+ 
diff --git a/docs/FAQs/README.md b/docs/FAQs/README.md
index 063bf1b..f9b6b74 100644
--- a/docs/FAQs/README.md
+++ b/docs/FAQs/README.md
@@ -1,6 +1,7 @@
 ## Frequently Asked Questions
 
 1. [How can I Inspect app-db?](Inspecting-app-db.md)
+2. [How do I do full-stack re-frame?](FullStackReframe.md)
 2. [How long after I do a dispatch does the event get handled?](When-Does-Dispatch-Happen.md)
 2. [How can I use a subscription in an Event Handler](UseASubscriptionInAnEventHandler.md)
 2. [How do I use logging method X](Logging.md)