InfoQ

InfoQ

Presentation

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Recorded at:
Recorded at

Thoughts on the Generic vs. Specific Tradeoff

Presented by Stefan Tilkov on Nov 03, 2009 Length 00:56:46
Sections
Enterprise Architecture,
Process & Practices,
Development,
Architecture & Design
Topics
REST ,
Architecture ,
Language ,
Methodologies ,
Domain Specific Languages
Tags
HTML 5 ,
UML ,
HTTP GET ,
Database ,
QCon London 2009 ,
XML ,
HTTPPost ,
QCon ,
Content Management Systems
The next QCon is in London March 5-9, Join us!
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
What is better, a generic solution or a specific one? Stefan Tilkov’s answer is “It depends.” He compares XML vs HTML, DSM-UML, Internal-External DSL, SOAP-REST, and others, outlining the advantages and disadvantages of each solution, showing that there is no certain answer to an architect’s quest to solve his problem, but there are some guidelines helping along the way.

Bio
Stefan Tilkov is co-founder and principal consultant at innoQ, a technology consulting company with offices in Germany and Switzerland. He has been involved in the design of large-scale, distributed systems for more than a decade, using a variety of technologies and tools ranging from C++ and CORBA over J2EE/Java EE and Web Services to REST and Ruby on Rails.

About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Sounds familiar by Michał Rembiszewski Posted
Re: Sounds familiar by Thomas Tarnow Posted
+100 by Sakesun Roykiattisak Posted
Brand New Thing Machine by Andreas Kleffel Posted
  1. Back to top

    Sounds familiar

    by Michał Rembiszewski

    It was a very nicely put dilemma with good examples, congratulations!

    I found one important for me point missing there though, which is code maintenance. I do agree forcing a generic solution to a peculiar problem often results in extra tedious and unnecessary work. Sometimes when the choice is not so obvious I would also consider the fact a generic solution might save you a couple thousands lines of code. These lines might be easy to write but you will have to maintain them later. And if they are easy to write you might be tempted to have them written by a novice developer which certainly won't help the code readability. So maybe it would be better to have a hundred lines of clumsy configuration after all in such case?

  2. Back to top

    +100

    by Sakesun Roykiattisak

    Really like the presentation

    "It depends.." .. A truly generic answer :)

    Probably, a generic solution is merely a specific solution to a set of similar problems.
    Unfortunately, most of the time there is no definition for that similarity.

  3. Back to top

    Re: Sounds familiar

    by Thomas Tarnow

    I have always found the generic home build frameworks much harder to read, test and debug than the specific and perhaps boring solution.
    Even worse is the specific and undocumented configuration DSL that you invent for your generic framework. It might work for you but 'then come the next guy'.
    I would say go for the safe solution, the solution that you know will work. Boring code is very quick to write, it's the thought of repeated work that is hard to cope with. Then when you have a working solution, look for patterns, refactor and generalize.
    I would worry more about the novice architect than the novice developer.

  4. Back to top

    Brand New Thing Machine

    by Andreas Kleffel

    the app framework of devexpress www.devexpress.com/Products/NET/Application_Fra... is a perfect example.

Educational Content

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

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?

Wrap Your SQL Head Around Riak MapReduce

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.