Questions for an Enterprise Architect
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Getting Started with Stratos - an Open Source Cloud Platform
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
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.)
I normally listen to the presenations when commuting.
Why there's no audio to this presentation posted?
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Andreas talks about the benefits of the Open Web and how it compares to proprietary stacks. He also talks about various projects that push the envelope like Boot to Gecko, Broadway and pdf.js.
Ron Bodkin discusses early adoption of Hadoop, NoSQL and describes MapReduce and related libraries and Frameworks. Other topics include Hive, Pig, multi tenancy, and security in a big data environment
Stephen Bohlen explains how Spring helps with interoperability between Java and .NET, demoing it with the help of a sample application.
Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.
6 comments
Watch Thread Reply