I am working with several building industry providers that
provide aluminum parts for storefronts. Each one of their catalogs "db tables" will be similar in structure.
I need a way to break down the cost for a publish / subscribe type of implementation.
I'm sure on the publish side that I'll need some type of cost break down like a staging area or something to that nature. In other words each providers catalog will be a little different so I need to transform that initial data published by the provider to
all merge together into one data base set of tables and the different catalogs be filtered by brand.
Exposing the subscribing portion of all this is not something I'm concerned about, it is having all the different providers publish to a proxy server and what is the cost for accepting those catalogs and transforming them into one data base that is filtered
by brand.
Example usage: On the end users end when they begin to draw a new CAD elevation they'll choose a brand and by choose that brand only the parts for that catalog will be used for that brand. If the provider of the catalog updates a parts price or removes a part
it is propagated to the subscriber.
What are some community suggestions that can I get started on a break down for the cost for creating a cloud based system like this, "In a man hour type of cost structure"? It doesn't have to be to technical I just need a few areas to get started.
Basically we're bring a specific industry catalogs "parts" to the cloud, Our Cloud with new servers and SQL Server instances.
I'm sure no matter what industry it would be for the methodology would be the same to transform published catalogs so the subscribers are exposed to ONE interface. This one interface allows access to a specific brands catalog by the user selecting the brand.
- Moved by Kalman Toth Wednesday, February 19, 2014 9:18 PM Not db design


