使用yml作为数据引用。 馊主意？

Question

I need about 1,000 words to be able to be accessed constantly by my app. The reason I want it detached is so that down the line, I can dynamically change what those 1,000 words will be.

But I don't necessarily feel this requires a database injection. I feel a simple .yml file could work.

Is this a good practice? And if it is, what would be the best way to do this?

Is it ok to load the 1,000 words in a before_filter call ?

Answer 1

Don't think that architecturally this is the right call.

If those are to be changed rarely, then you can put them inside a constants class. If you plan to change them often, what you will do is write to file system and read from it which is exactly what every database does, but in a much much faster and optimal way then you could possibly write.

My two cents. Let us know how it worked out.

Answer 2

Do not use relational database unless you really need to. If your "words" are relatively immutable, can be accessed simultaneously without multithreadig concerns, you do not need querying etc - they are better off in some hash loaded for entire applications on startup loading them for every reuest is not a good idea. ( this advice is not related to ROR )