Re: Design advice needed
- From: "Nick Malik [Microsoft]" <nickmalik@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 22 Oct 2005 09:42:08 -0700
Hello Lothar,
In my experience, having a layer that cannot be customized in code to allow
the addition of business rules, or to allow integration with other systems,
is a waste of time and energy.
There is a REASON for every layer of code. Seperating the database from the
front end can be done using a number of packaged solutions both within some
frameworks and as add-ons, IDE plug-ins, and other tools. However, the
strongest of them allow you to modify that layer in some way. Yes, they do
the "grunt-work" but they don't lock you out of the detailed work that needs
to be done in the business objects layer.
To look at some of the products out there, search for "Data Transfer
Objects" and "Object Relational Mapping" concepts using MSN Search or
Google.
Do us all a favor and resist the temptation to add another one of these
critters to the software universe.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
<lothar.behrens@xxxxxxxxxxxx> wrote in message
news:1129711296.024033.12730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I am developing an application wich uses a database model to retrieve
> it's configuration on how to build up the database application.
>
> It is like a prototype for any database application, you could use it
> very
> early in a development cycle. But it is too slow.
>
> I want to fasten it up with some kint of caching or the like. I know,
> there
> are persistence layers and other techniques to be used for this, but I
> don't
> know where to start exept to create a 'document' interface for the
> application.
>
> In the implementation of the document I think about general functions
> like
> sync, save, load and to get the values for specific entities, I like to
> use
> get and set functions like this:
>
> char* getElement(char* nameOfElement);
> void setElement(char* nameOfElement, char* value);
>
> documentPart* getElement(char* nameOfElement); // Container
> void setElement(char* nameOfElement, documentPart* value);
>
> This is like DOM.
>
> My requirements are as follows:
>
> * Should syncronize with the database,
> * Should store a local copy (replicate)
> * Should add a layer between the application and the database.
> * May be able to use hooks to save/load data with my database classes
> * LGPL
>
> If there is nothing to be used, I like to ask for matching patterns
> that
> are related to these requirements.
>
> Thanks, Lothar
>
.
- References:
- Design advice needed
- From: lothar . behrens
- Design advice needed
- Prev by Date: Re: 3GL vs. 4GL [was: Re: LSP and subtype]
- Next by Date: Re: Understanding OO Code
- Previous by thread: Design advice needed
- Next by thread: [UML] Full lines between Use Cases
- Index(es):
Relevant Pages
|
