Commanding Chaos for Coworking, Open Source and Creative Communities

Features driven development -- the nitty gritty and thoughts on the future of sustainable "in code" development | aWebFactory

Thu, 02/02/2012 - 06:56 -- rprice

Modern multitier software architecture allows us to separate concerns when we are building a web application. For example, when there is a request to visualize a content item in Drupal, the request is handed off to a logical handler (module), which should be using some kind of API to read the necessary data from the database. And once it has assembled that data it should invoke the theming engine and its current theme in order for the final output to be rendered all ready to be sent back to the browser that made the request in the first place. So this separation of concerns means that the code responsible for each _tier_ are separate from code in the other tiers. And the benefits are greater simplicity of each separate piece compared to the single monolithic block, and hence fewer bugs and greater ease and flexibility in when it comes to modifying code. So, code is housed in different tiers. Hold that thought.