• View
• Edit
• History
• Print

(:addthis:)

CoEvolution > Oimp > CloudArbitrage-Schemas

back to the Cloud Arbitrage

Overall principle

(:pmgraphviz -- digraph { factor_n [label = "factor f"]; subgraph cluster_vendors{ vendor_1 [label = "vendor 1"]; vendor_n [label = "vendor n"]; } client_code [label = "client code\n(set of restrictions)"]; vendor_1 -> vendor_n [label="cost of moving code"]; factor_n -> vendor_1 [label="impacts prices"]; factor_n -> vendor_n [label="impacts prices"]; cluster_arbitrage_solution -> vendor_n [label="estimate behavior"]; cluster_arbitrage_solution -> vendor_1 [label="estimate behavior"]; cluster_arbitrage_solution -> factor_n [label="estimate behavior and impact"]; client_code -> cluster_arbitrage_solution [label="looks for the best environment"]; cluster_arbitrage_solution -> client_code [label="pick environment"]; } :)

Internals

(:pmgraphviz -- digraph { client_code [label = "client code\n(set of restrictions)"]; subgraph cluster_arbitrage_solution { label="arbitrage solution"; set_of_factors -> model; model -> simulations -> choosing_vendor; } choosing_vendor -> client_code; client_code -> model; } :)

Resource allocation

Make a schema regarding impact factors -> ordering -> lowering the cost of simulation while augmenting accuracy -> improving margins

This is basically our core process since it is our added-value. We provide this service in order to make the client focus on his own core process.

The better we are able to predict on the longest term with the lowest amount of resources spent, the more gain we can make.