• 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Factory Home Doubt

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

I am working on Factory Homes Assignment. I am dealing with the following architectural decision:

1)Do we need to persist in the Factory Homes DB the components that the user have selected to create the house? I would want to avoid it because this will mean to replicate the same entities/tables (wall, roof, ....) aleady present in InventorySystem.

Since that the Factory Homes is owner of the InventorySystem, I think that an alternative could be store directly in InvetorySystem the components that are seleced from the user and wtht an external key we could retrive it in Factory Homes the components that compose a copleted design.

What do you think of this?

Thanks in advance,
Mimmo
 
author & internet detective
Posts: 40746
827
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mimmo,
As I recall, you aren't designing the Inventory system. I wouldn't assume you can refer to it because I think it oversimplifies the problem.
 
Mimmo Ludovico
Ranch Hand
Posts: 49
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Jeanne,

you are right that we are not designing the inventory system, but if what I asked/thought could be right then I will put it in the list of the assumptions. Because when you are designing a system that need to interact with external system, that are maintained from the same company, then it could be reasonable to require some small modifications to the external system
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Mimmo Ludovico wrote:Hi All,

I am working on Factory Homes Assignment. I am dealing with the following architectural decision:

1)Do we need to persist in the Factory Homes DB the components that the user have selected to create the house? I would want to avoid it because this will mean to replicate the same entities/tables (wall, roof, ....) aleady present in InventorySystem.

Since that the Factory Homes is owner of the InventorySystem, I think that an alternative could be store directly in InvetorySystem the components that are seleced from the user and wtht an external key we could retrive it in Factory Homes the components that compose a copleted design.

What do you think of this?

Thanks in advance,
Mimmo



I am working on it too. Well in my understanding Inventory System is to be considered "immutable". A black box used only for what it is described in the spec.
However, due to my past works and experience, I was thinking to get rid of a DB by using a CMIS enabled ECM, such as Alfresco, Share Point etc. This way I could store and retrieve the XML, and all rendered stuff (video, jpg, etc..).
 
The moustache of a titan! The ad of a flea:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic