Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Recorded at:
Presented by Eric Evans on Sep 03, 2009
Technical Debt and Design Death
The 5 Mandates of Software Development Teams - Presto Manifesto
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
Architectures Behind Facebook, Skype, Sky.com, Bwin, League of Legends @ QConLondon
Eric Evans obviously is a very good speaker.
Eric's ways seems much like the SOA concept, wrap the legacy system and map the different model; reuse the services to make the new features.
I almost quit the industry until 2/3 of the way through when he admitted he was probably depressing responsible architects and designers :-)
Yes, it does sound like the SOA technique of wrapping Legacy systems, that's hardly a new concept, but with 22 years experience, I don't find any of Eric Evans ideas are new, but I do find it nice that he's bundled them together and is evangelizing the importance of good engineering and design practices and domain modelling in particular.
Fully agree with the content and the proposed method. The problem is, that many large companies have huge legacy "system-landscapes" (=big balls of mud) that have successfully survived previous attempts to migrate, clean-up etc. and meanwhile their maintenance is so expensive that phasing them out is a must from purely a financial point of view.
What I notice is that usually these companies start every 3-5 years such initiatives as described at the beginning of the presentation and end up in the same situation (year 2 usually means the end of it). Due to the fact that after such failures usually the management is also exchanged, it is almost impossible to have any discussion about a different approach...
Spot on. It takes more than 2 years to replace these large IT systems but that's as long as management is willing to wait, so they always fail.
The trick is to cut the thing into pieces and have staged deliverables. Sometimes that's not easy, when like you said, all you have is a big ball of mud (or as I like to describe it, a sagging carboard shanty that the users want you to wallpaper, add gold faucets, and hang a chandelier in.)
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.
5 comments
Watch Thread Reply