Ruby on Rails Friday, August 19, 2016

On Thu, Aug 18, 2016 at 8:18 PM, Phil Edelbrock <edelbrp@gmail.com> wrote:

> it is
> banking information and we're supposed to not store that stuff in order to
> be PCI compliant.

How does PCI define "store"? If it's OK to have it in *RAM*, just not
on *disk*, maybe you can "store" it long enough to launch the
background task, in something like Redis -- just make sure it's never
flushed to disk.

Alternately, perhaps you can fire off an asynchronous request to
another system (whether on the same box or no) that could handle the
tasks. IIRC, PCI will require that it be protected in transit so
there's all that overhead, but even so, there may be some
possibilities along those lines.

--
Dave Aronson, consulting software developer of Codosaur.us,
PullRequestRoulette.com, Blog.Codosaur.us, and Dare2XL.com.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAHxKQihzgraBsh9rO3vOZsNbaM8K5yxqB8fierPM1DRvV188aQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment