Re: How-to implement the e-Commerce-System found in the "IDDD" book

> 
> I was when I started this thread unsure if the process of creating
> 3 BCs was worth the extra work.
> But  I am already getting some help here on how-to build the models so this must be good (-: 
> 
> Yes the invoicing needs to historicly store its data. I therefore
> could use a read database schema for this. 
> 
>  Most of my invoice logic takes place when "creating" an invoice. The user kind of works in a excel sheet (ajax enriched form) where he can turn on and off lots of knobs. Since the created invoice may need to refer to past invoices I am not sure if the read database might even complicate things.(Also the ajax Interface by no means is a task oriented interface)
> Scenarios like create invoice A. publish Event "Invoice A created"
> create Invoice B that refers to Invoice A. But maybe Invoice A hasnt been yet saved to the read database. But on the other hand a read database architecture does also seem very helpfull for dealing with
> historical data.....
> 
>  

In what scenarios would you need to refer to another invoice from one invoice? I.e. what's the use case for this?




------------------------------------