On Wed, Oct 1, 2014 at 5:58 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:
None of the logic that is specific to your application is going to live in the database<
That just does not sound right to me; but I don't remember ever disagreeing with John,
so I'm maybe I'm very much mistaken (happens all the time).
No worries. Keep in mind I was just giving my interpretation of what
the article said, so if you're disagreeing with *me* then you're
saying that you interpreted the article differently. If we both
understand the article the same, and you're disagreeing with the
article, that's a completely different matter.
However, being a total DB bigot, I would say as much of the application as possible
should be developed in the database if the goal is data integrity.
Otherwise, just use Evernote ?
I will say that I'm not particularly tied to one model over another.
I think practically every scheme has advantages and disadvantages and
addresses some kind of need (otherwise why would people dream them
up?).
I'm not even sure that the article was saying that back-end
development was a *bad* idea, just that
front-end-first(-and-maybe-only) development is growing, particularly
for Web applications, that there are good reasons for this trend, and
that it happens to be what the author engages in himself. Some quotes
from the article:
"Only using back-end services when needed and only doing so from the
client is certainly not the ideal architecture for every application.
In many cases, thinking of the back-end as a set of independent black
box services is just not realistic."
"Will Front-end Driven Applications Take Over The World?
I have no idea what the repercussions of building FDA’s will be, or if
it will even gain mainstream mindshare."
The article actually struck me as pretty reasonable. (So I guess some
folks will definitely have some disagreement with me on that. :)
John Y.
midrange.com
