• 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
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Frank Carver
  • Henry Wong
  • Ron McLeod
Saloon Keepers:
  • Tim Moores
  • Frits Walraven
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Himai Minh

Application Architecture Suggestion

 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Everyone,

I am throwing a question about the application architecture, not really related to the certification. Please answer me considering, I am not very expert on application architectures.

I want to design a learning web application that contain Four components given as follow; I have split first three components as a separate Java/EJB project in Eclipse, Web is naturally a web project. Now, Here I am having two questions, given below;

1- Sales Component
2- Purchase Component
3- Inventory Component
4- Web Interface Component

Questions:

1- Is that a right way of splitting at component/project level? If not please suggest the right/appropriate/standard way.
2- About the DAOs for each of first three component, Should I keep them as a separate package in these projects or define a separate project for them?

Please suggest any books, sources to address these type of architectural decisions.

I would really appreciate your early attention.

 
Run away! Run away! Here, take this tiny ad with you:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic