lozand / Portfolio_App

Stuff to do things
0 stars 0 forks source link

Make design decisions on the decision engine and other external APIs #10

Open lozand opened 8 years ago

lozand commented 8 years ago

I need to figure out what the best way to move forward is after the core is done. There should be some other layer that calls out for information as needed and writes it to the database, but it doesn't necessarily need to live in the core layer. Also, the decision engine needs to live somewhere. Should it be a service? Just a library? Is it on a timer? When does it make decisions? What triggers it? What's the best way to do all this? Should I expose the data layer to this API layer? Should I use WCF?