State should not depend on the API server

[Ian Booth]

On 01/09/14 16:03, John Meinel wrote:
> FWIW I'd favor 3 layers, though it does mean you have to do copying between
> structs that would likely otherwise be almost identical. A State layer for
> saving in the DB, an API layer for communication, and a Model layer for use
> in the Agents/Clients.
>

This is my wish too. A sane, layered architecture, devoid of inappropriate
coupling between layers, and a proper separation of concerns; the result of
which will lead to, amongst other things, much better and faster, true unit
tests. Well, there's a bit more that needs fixing first, eg more IOC, less use
of concrete structs etc, but our current woes with unreliable tests is directly
attributable to the fact that we often need to bring up the entire stack to test
a component.

So any progress towards fixing things, in this case eliminating unnecessary and
inappropriate coupling between state and api server is much appreciated.


> John
> =:->
> 
> 
> 
> On Mon, Sep 1, 2014 at 9:40 AM, David Cheney <david.cheney at canonical.com>
> wrote:
> 
>> Hello,
>>
>> This is an introductory email to explain my upcoming series of pull
>> requests.
>>
>> The theme is simple: state must not depend on the api server.
>>
>> This is currently not true, state depends on api/params because some
>> of the api types have leaked into the state package and are being
>> directly stored in mongo.
>>
>> Please speak up if you disagree with this proposal.
>>
>> Dave
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
> 
> 
>