CLOSE FULL VIEW
Learning from Five Years as a Skype Architect
Recorded at:
Community comments
DB and business logic
by
Robert Sullivan
Posted
nice presentation
by
Leandro Coutinho
Posted
DB and business logic
by
Robert Sullivan
Good to hear that not all have pursued the fad of storing all the business logic in the middle tier, as we've been told by many gurus. After building some significant stored procedures, and then pondered the corresponding complexity of J2EE EJBs and/or Hibernate and burying the logic in xml, and coming to the same conclusion as Andres, I will meld a couple of his points - the architecture needs to fit the organization, and simple is good.
Maybe business logic in the db is not a good fit for everybody, but we must stop blindly accepting the latest wisdom as the end-all be-all truth.
The pgQueue was very interesting idea also, especially simplifying from once-and-only-once to at-least-once. There was a post recently here on Infoq that was about a very similar idea, except it was unfortunately a little misleading in that, perhaps for fanfare, it stated that there was no need for a queue. But they were still building all the queue infrastructure, it was just a simplified queue. So the idea of a queue structure still holds and is very useful, as can be illustrated in languages like Erlang, which supports concurrency nicely, offering tremendous performance.
It would be very interesting to hear more about this design, and also the various tools available from Postgres that were mentioned.
Thanks for the interesting talk!
Maybe business logic in the db is not a good fit for everybody, but we must stop blindly accepting the latest wisdom as the end-all be-all truth.
The pgQueue was very interesting idea also, especially simplifying from once-and-only-once to at-least-once. There was a post recently here on Infoq that was about a very similar idea, except it was unfortunately a little misleading in that, perhaps for fanfare, it stated that there was no need for a queue. But they were still building all the queue infrastructure, it was just a simplified queue. So the idea of a queue structure still holds and is very useful, as can be illustrated in languages like Erlang, which supports concurrency nicely, offering tremendous performance.
It would be very interesting to hear more about this design, and also the various tools available from Postgres that were mentioned.
Thanks for the interesting talk!




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think