Re: Front-end Driven Applications

On Fri, Oct 3, 2014 at 9:41 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/2/2014 5:30 PM, John Yeung wrote:

So in your case, you have some coordination between front-end
and back-end development, and every time you make a custom stored
procedure, you're increasing the coupling between the front and back
ends.

That would be true if I designed the SP to be tightly coupled to the
front end, but I've been seriously labouring to make those SPs usable by
my own code base as well. It's been a mixed success, but just thinking
about that tends to make these procedures general purpose APIs as
opposed to specific one-offs.

I fully appreciate and respect your toolmaker sensibilities (which I
share to a large degree). But again, that's a back-end-oriented view.
While you may not have increased the degree to which the back end is
shaped by the front, the fact that the front end is now relying on
your SP means that the front end is now molded a little more tightly
to your specific back end and is a little less portable to other back
ends.

I'd also like to note that the author of the FDA article may or may
not be as decoupled as he purports (since, as Nathan points out, he
seems to be shilling for Telerik).

John Y.