Managing important runtime business logic with regard to a codebase

Posted by Daniel Beardsley on Stack Overflow See other posts from Stack Overflow or by Daniel Beardsley
Published on 2010-04-13T20:54:36Z Indexed on 2010/04/13 21:03 UTC
Read the original article Hit count: 280

Filed under:

business-logic

|

database-design

|

version-control

|

web-applications

I'm working on a project which will end up have a lot of application information stored in the form of records in a database. In this case, it's the configuration of data views:

which grid columns to show/hide
default filters to apply to each grid view
column titles
sorting
subtotaling
...

This information is a big part of the value of the application and is essential to it's function. The data will be altered by admins a fair amount, so it's not static and it wouldn't be appropriate to have to deploy a new version of the app every time the data changes.

The question is, Where should this data be stored? It will definitely live in the database because that's how it's accessed, but I feel like it needs to also be kept with the version controlled codebase because it's an integral part of functioning of the application. Has anyone dealt with an issue like this before? What did you end up doing?

© Stack Overflow or respective owner

Related posts about business-logic

Project structure: where to put business logic

as seen on Programmers - Search for 'Programmers'
First of all, I'm not asking where does business logic belong. This has been asked before and most answers I've read agree in that it belongs in the model: Where to put business logic in MVC design? How much business logic should be allowed to exist in the controller layer? How accurate is "Business… >>> More
Business Logic Layer Pattern on Rails? MVCL

as seen on Stack Overflow - Search for 'Stack Overflow'
That is a broad question, and I appreciate no short/dumb asnwers like: "Oh that is the model job, this quest is retarded (period)" PROBLEM Where I work at people created a system over 2 years for managing the manufacture process over demand in the most simplified still broad as possible, involving… >>> More
Does business logic belong in the service layer?

as seen on Stack Overflow - Search for 'Stack Overflow'
I've got a set of classes, namely, a data transfer object, a service implementation object, and a data access object. I currently have business logic in the service implementation object; it uses the dao to get data to populate the dto that is shipped back to the client/gui code. The issue is that… >>> More
Transforming Business Logic into Web Services Using DB2 9.5 and IBM Data Studio

as seen on Internet.com - Search for 'Internet.com'
Learn how to take business logic such as stored procedures, functions, or SQL statements and turn them into a Web service. >>> More
SQL Server 2008: CASE vs IF-ELSE-IF vs GOTO

as seen on Stack Overflow - Search for 'Stack Overflow'
I have some rules in my application and I have written the business logic of that rules in my procedure. At the time of creation of procedure I came to know that CASE statement won't work in my scenario. So I have tried two ways to perform same operations (using IF-ELSE-IF or GOTO) shown as below… >>> More

Related posts about database-design

(Database Design - products attributes): What is better option for product attribute database design

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi, I new in database design. What is better option for product attribute database design for cms?(Please suggest other options also). option 1: 1 table products{ id product_name color price attribute_name1 attribute_value1 attribute_name2 attribute_value2 attribute_name3 attribute_value3 } option… >>> More
Book Review: Pro SQL Server 2008 Relational Database Design and Implementation

as seen on SQL Blog - Search for 'SQL Blog'
Investing in proper database design is a very efficient way to cut maintenance costs. If we expect a system to last, we need to make sure it has a good solid foundation - high quality database design. Surely we can and sometimes do cut corners and save on database design to get things done faster… >>> More
Advice on database design / SQL for retrieving data with chronological order

as seen on Stack Overflow - Search for 'Stack Overflow'
I am creating a database that will help keep track of which employees have been on a certain training course. I would like to get some guidance on the best way to design the database. Specifically, each employee must attend the training course each year and my database needs to keep a history of… >>> More
Fiscal year handling strategies in database design

as seen on Stack Overflow - Search for 'Stack Overflow'
By fiscal year I mean all the data in the database (in all tables) that occurred in the particular year. Lets say that we are building an application that allows user to choose from different years. What way of implementing this would you prefer, and why: Separate fiscal year data based on multiple… >>> More
Database design for summarized data

as seen on Stack Overflow - Search for 'Stack Overflow'
I have a new table I'm going to add to a bunch of other summarized data, basically to take some of the load off by calculating weekly avgs. My question is whether I would be better off with one model over the other. One model with days of the week as a column with an additional column for price… >>> More