Now that I caught your attention with the strange title of this post, I will explain to you what flannel programming means.  Any good developer and/or consultant should have some way of separating their applications into different layers.  This is usually called a “Pattern”. I usually apply the term “Flannel” to the pattern we use in our applications at Teraeon Consulting.

In the last post I wrote about the importance of looking at your enterprise application as a large system made up of smaller systems.  Now I’m going to talk about the importance of further separating your application into a pattern.

What are Patterns?

Patterns are the physical separation of code into different segments.  These segments typically are your Data Layer, Business Logic, and finally Presentation.  What you use for these different layers is typically up to the company.  Many companies that use J2EE for example use EJB’s as their Data Layer, while in .NET you might use strongly typed datasets.

The separation of code into layers, allows you to centralize code into these areas making it much more usable.  You would be surprised at how many Internet Consulting companies are still writing scripts that have no centralization, or code re-usability whatsoever.    Get more information Layered Architecture

Tags: architecture, business logic, enterprise application, Internet Consulting, usability

This entry was posted on Saturday, February 7th, 2009 at 10:15 pm and is filed under Business Process Improvement, Business Technology, Platforms, Web Applications, Web Technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.