A couple of thoughts I had looking through this thread...
First, storing the key in shared memory is fine, but permissions changes between API calls won't be reflected until the key expires. This may or may not be a big issue for you, but you should consider the security implications of your time-to-live. You can always set a short TTL (60 - 120 seconds) but that kinda defeats the purpose.
Second, I would give some serious thought to whether or not the constant database hits would actually be detrimental to your app. How many requests are we talking about? 100 per minute? 1,000 per minute? 1M per minute? 1 per hour? I wouldn't design for scale until you have an actual need to scale.First, storing the key in shared memory is fine, but permissions changes between API calls won't be reflected until the key expires. This may or may not be a big issue for you, but you should consider the security implications of your time-to-live. You can always set a short TTL (60 - 120 seconds) but that kinda defeats the purpose.
On Wed, Nov 13, 2013 at 1:16 PM, <jtracy717@gmail.com> wrote:
I appreciate the guidance, guys. Nice to know I'm covered at my current scale and have some good options to look at if I need to scale up.
--On Wed, Nov 13, 2013 at 7:58 AM, David Mitchell <jdavidmitchell@gmail.com> wrote:This may be a matter of preference, but my first choice would be Redis. My second choice would be memcached. But, as Oscar said, "If you don't need to share that key across web servers, APC will work just fine."David
You received this message because you are subscribed to the Google
Group: "Washington, DC PHP Developers Group" - http://www.dcphp.net
To post, send email to washington-dcphp-group@googlegroups.com
To unsubscribe, send email to washington-dcphp-group+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/washington-dcphp-group?hl=en
---
You received this message because you are subscribed to the Google Groups "Washington, DC PHP Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to washington-dcphp-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google
Group: "Washington, DC PHP Developers Group" - http://www.dcphp.net
To post, send email to washington-dcphp-group@googlegroups.com
To unsubscribe, send email to washington-dcphp-group+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/washington-dcphp-group?hl=en
---
You received this message because you are subscribed to the Google Groups "Washington, DC PHP Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to washington-dcphp-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
0 comments:
Post a Comment