NYCPHP Meetup

[Mitch Pirtle]

This is what REST was intended for.

You don't need to limit yourself to one database; and you don't need
to tie to any specific language. Scale shouldn't be limited by a
single database either...

By providing a REST API to your data, you push the concept of stored
procedures up the stack, making it a LOT easier for you to scale the
database as there's no reliance on stored procs.

Second, any language talking HTTP POST/GET is able to interface with
your REST systems, freeing you to choose the right tool for the job.
PHP, java, ruby, whatevah!

Third, REST can also be load balanced across many systems, greatly
simplifying your needs when it is time to scale the system out.

Fourth, REST can be load balanced by URL - assuming you have a half
decent load balancer - so you can segment your REST services based on
function: Authentication, Registration, Purchase, etc.

This is really a perfect situation for a REST service, and you should
consider it.

And on alternative database engines, MongoDB also will have a huge
impact on your development, as you're able to do a lot of
"unthinkable" things that just don't work in the old relational model
- such as your "insert once, update many counters" example is a
perfect fit. MongoDB is great for real time analytics and some pretty
high traffic sites can attest to how well MongoDB performs in that
scenario.

-- Mitch

On Mon, Nov 30, 2009 at 11:25 AM, Daniel Convissor
<danielc at analysisandsolutions.com> wrote:
> Hi Matt:
>
>>> All of them work and they're all pretty much the same when it comes to
>>> the programming language layer.
>>
>> Except for when the programmers you're working with don't want to/aren't
>> strong at writing SQL.  Which is the case here, and I need more to do,
>> hence wanting to put some of the DB logic in the database.
>
> Just to be clear, what I'm saying is the act of inserting the data is
> pretty much the same regardless of the route.
>
> But, as you're initially asking, several steps need to be performed after
> the record is inserted, then stored procedures are handy.
>
> --Dan
>
> --
>  T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
>            data intensive web and database programming
>                http://www.AnalysisAndSolutions.com/
>  4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409
> _______________________________________________
> New York PHP Users Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/Show-Participation
>