I am quite serious when I ask for more specifics on the types of integration primatives you are talking about? My experience has been the opposite here are som

I am quite serious when I ask for more specifics on the types of integration primatives you are talking about? My experience has been the opposite here are some examples: Number of times I had to implement or maintain hand rolled queues in the database. Number of times I had to implement a web service whos only purpose was to expose database data to the world. Number of ETL processes I wrote just to handle some data daily data input from a third party. Number of times I had to use comparatively complex SQL techniques to iterate over a list of rows because SQL is intended for set based operations not iterative processing .. Number of times I had to do tedious text templating to generate HTML or XML or JSON or any kind of heirarchical data format that is easily consumable by a non database system. That's what I am talking about Which isn't to say this is a bad architecture. Just that database as integration platform has its challenges, a lot of them.