That means these are all
important questions that you should be asking yourself before you even begin to write your
first bits of code.
Let??™s examine some of the finer points about each of these questions now, so we can make
more informed design decisions about our applications.
How Much Do You Want to Do in Active Record?
Traditional database applications are considered N-tier applications precisely because they
involve multiple tiers of complexity. That is, multiple applications run independently from
each other but are connected in some fashion so as to run a unique and complete process
together, handing data back and forth between the tiers of complexity as needed. Usually,
each tier would be responsible for processing the data in some way before handing the resulting
data off to the next tier.
This meant that for a simple database application you could potentially need both an
application developer and a database developer (or database administrator depending on
how your company views the various roles). Among the people involved, knowledge of the following
was a bare minimum to get an application working:
??? Application programming syntax and concepts
??? How your language of choice communicates with your database of choice
??? The SQL syntax your specific database requires
??? How your database of choice handles various SQL statements and requests
That??™s a lot of knowledge required to build even the most basic application.
Pages:
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368