5 reasons why database integration sucks

[Paul Williams]

The architectural (anti?) pattern database integration is a subject close to my heart, and I've now blogged about it. Would appreciate any feedback or discussion.

Paul.

[Jonathan Willis]

Funny you should post this today. Neil had me looking at onion architecture. The focus been pushing the database to the system edge much like the ui, it's an implementation detail and subject to change.

This part has the best diagrams in my opinion. http://jeffreypalermo.com/blog/the-onion-architecture-part-3/

Sent from phone

On 18 Mar 2013 11:25, "Paul Williams" <pa...@paulswilliams.me.uk> wrote:

The architectural (anti?) pattern database integration is a subject close to my heart, and I've now blogged about it. Would appreciate any feedback or discussion.

Paul.

--
You received this message because you are subscribed to the Google Groups "Agile Staffordshire" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilestaffordsh...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Paul Williams]

Jonathan, 

Even funnier is that I was only listening to Ruby Rogues Rescue projects this morning discussing the concept of onion architecture, and it's USP - the ability to delve deeper through the layers for advanced use. Interesting, and I agree this is a good solution providing it's contained within an 'application'. 

I like the similarities with this an hexagonal architecture in pushing the database out, but I worry slightly about leaky abstractions. 

Unless I missed the point, I would be more resistant to this when dealing with multiple system integration; this is one area where the benefits are far greater than any costs - the likelihood of one side of a relationship is higher than re-architecting one system.

Rob started an alternative conversation on the blog post, but it would be good to continue this conversation. We're both of the feeling that this is a large 'elephant in the room' for many companies, and provide real issues to their ability to respond to change. More discussion might be able to provide more tangible advise, or results that could be useful to our peers in improving things. 

Paul

On Monday, March 18, 2013 6:33:58 PM UTC, Jonathan Willis wrote:

Funny you should post this today. Neil had me looking at onion architecture. The focus been pushing the database to the system edge much like the ui, it's an implementation detail and subject to change.

This part has the best diagrams in my opinion. http://jeffreypalermo.com/blog/the-onion-architecture-part-3/

Sent from phone

On 18 Mar 2013 11:25, "Paul Williams" <pa...@paulswilliams.me.uk> wrote:

The architectural (anti?) pattern database integration is a subject close to my heart, and I've now blogged about it. Would appreciate any feedback or discussion.

Paul.

--
You received this message because you are subscribed to the Google Groups "Agile Staffordshire" group.

To unsubscribe from this group and stop receiving emails from it, send an email to agilestaffordshire+unsub...@googlegroups.com.