Stored procedures, if used sensible, are the layer between your program code, and the physical data layout. You could implement business rules in your stored procedures, but you don't have to.

As for stored procedures being the "backend", that's just a matter of perspective. Properly designed systems have many layers, and stored procedures are just one layer. If you put that layer in the "backend", it's in the backend. If you consider that layer part of the middle-tier, it's part of the middle-tier.

You should put your business logic where it makes the most sense for your solution. Don't worry too much about what lable is put on it. Don't chase buzzwords.

Abigail

In reply to Re: N-tier, client/model, and business rules? by Abigail-II
in thread N-tier, model/view, and business rules? by LameNerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.