Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
Recorded at:
Presented by Jan Lehnardt on Aug 14, 2009
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Regaining control of the data centre
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Hi Jan,
nice presentation. However, I still don't get how CouchDB overcomes the issue with generic DB Schema. You mentioned in the minutes 11.45, that it is not good in performance, because of the JOINS. But the reason to have a generic DB Schema is because the developer want to make the application flexible. So everytime there is a new function needed, he does not need to create a new DB or a new class. Do you have answer for this?
Gruß aus Heidelberg,
Steve
Very interesting talk, is part II doing going to be posted? Jan said a lot of the answers to questions asked were in the 2nd part.
Nice presentation.
Although you are not a very good speaker.
Dragan, oh boo! I'm not a native speaker and this was a very prestigious crowd. Can you point to any specific shortcomings? :) Thanks for the feedback anyway.
@Steve, CouchDB doesn't make schema migrations go away, it just lets you do be lazy with them as you don't have to do them upfront. CouchDB views and show functions (not mentioned as they weren't invented then) can morph you docs into anything you need.
It is a trade-off question, if you can afford a 9-table JOIN and live with the performance implications, that's fine. Large websites do run without a single JOIN because they can't.
In addition, not all data is inherently relational. Being able to store things flexibly makes for more natural data handling, less code, less bugs, less headache.
Thanks for your question!
Nice presentation. Are you going to post the second part?
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
6 comments
Watch Thread Reply