• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

appropriate pattern for a database

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm starting to work on a app that will support a small business. It will have information stored in a database, such as employee data, employee hours, supplies, etc. It will also create reports on the information and allow a person to add and remove employees, stock either manually or because of changes in the database.
What I am try to determine is what type of design pattern I should use to make this a scalable app. I realized how useful patterns were after I designed an app with the factory pattern after reading the Head First Design Pattersn book, made it a breeze to modify the program. Anyway, I'm thinking it may be a combination of some design patterns. However, I'd like to get some input. I figure someone may have tried to do this before and maybe I can proactively avoid some of the pitfalls.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Tyler Jordan:
I realized how useful patterns were after I designed an app with the factory pattern after reading the Head First Design Pattersn book, made it a breeze to modify the program.



Maybe it is time to get into Patterns of Enterprise Application Architecture (PEAA) (amazon US) then.
As you can see in the P of EAA Catalog there are Data Source Architectural Patterns, Object-Relational Behavioural Patterns, Object-Relational Structural Patterns, Object-Relational Meta-Data Mapping Patterns.

Data Access Patterns: Database Interactions in Object-Oriented Applications (amazon US) is good too but I think PEAA is all around more useful. Also PEAA is a great companion book to Domain Driven Design � Tackling Complexity in the Heart of Software (home; amazon US). Though DDD is probably overkill for your current project.
 
Tyler Jordan
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, the book looks like just what I need. I had a feeling that I was moving beyond what the Head First Design Patterns can provide with this new project.

Thanks for the reference!
 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Tyler,

If its scalability you need and if you're using EJBs, make sure you use Stateless Session Beans as Session Facades to access your business objects.

Cheers.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I can only second the recommendation for the PEAA book!
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic