Who??™s Responsible?
When you are trying to decide just where to place various parts of your application processing,
another important issue to consider is who??™s ultimately responsible for that part of the processing.
Who??™s going to have to fix the problems when they appear (and trust me they will)?
If, ultimately, you are going to be the one responsible for maintaining the application and
all its related parts, and you??™re most comfortable within the Ruby realm, it probably makes
sense to keep as much as you can within that realm. On the other hand, if you need to share
responsibility, it might make more sense to move more of your application logic inside of the
database application and let someone else deal with all the related issues as they occur.
How Do Things Get Done?
Along the same lines of deciding where things get done and who should do them is to determine
just how things actually get done. Again, if you are the one who will need to actually
maintain the application, resolve issues, and apply updates, it might make sense to keep as
much as you can inside of the Active Record realm.
Pages:
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371