ruby - Best practices for populating rails with processed data -
For some data processing I am working on a program for a few months, and it is now on a platform where Instead of displaying information through the command line (stored via ActiveRecord), I would like to display processed information through a Rail app.
The first question I have to face is that I should have data processing and display data in the same application, or in different applications I have been adapting to different applications because the low code There is less chance of security issues (some data processing codes are slightly shorter and are vulnerable to optimization reasons).
The second question is how can I handle the database schema, if I split it into a rail display app and an offline data processor. Whether it should be given only a fully populated database for rail applications or should I provide a rail app with migration and / or schema rb?
Edit : The data processing application is for a Wikipedia's philosophical event. For the English version, it takes a 20GiB XML file and sees how ~ 6 million pages link to each other.
Actually can not say whether applications should be divided or not, without further reference.
The second question again, you can work fine without schema and migration, without fine-tuning 0.5 fences in the Rail without any of these fancy lore features.
Just make sure that you have a solid database schema that works evenly for both parts of your app (or both apps, depending on the way you go)
Comments
Post a Comment