![]() ![]() Each page is, normally, representedĪs a screen. Theįunctionality can be divided into the following distinct layers:Īpache OFBiz uses the concept of "screens" to Frameworks are a little oldie, but serve as a good source of inspiration.Īll Apache OFBiz functionality is built on a common framework. They provide very good documentation and a modular 3-tier architecture, as you mentioned in your question. I'd recommend taking a look at open source ERP/CRM solutions - Apache OFBiz could be a good option or starting point, since you have some Java expertise. ![]() Is it good way? What do you think?ĭesigning and implementing an ERP from scratch isn't an easy task, especially in your case, in which you have zero experience with this kind of application. This will be our default template and when customer will ask about change we will create another branch for that. ![]() Can you tell me what is the best practise for that use-case? What is recommended project structure? We have no experiences with this kind of software so I would ask you for help. Also need add another entity into domain model of module A which cause change in database, business process and also rest (changing of rest should cause change of frontend). Customer needs only A and B, where each module will have domain model, business layer, rest api. We are going to develop ERP which should be customizable for different customers, and also customer can tell which modules need and which not.įor instance: we got modules A, B and C. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |