{"action":"created","issue":{"url":"https://api.github.com/repos/domain-query-language/dql-server/issues/47","repository_url":"https://api.github.com/repos/domain-query-language/dql-server","labels_url":"https://api.github.com/repos/domain-query-language/dql-server/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/domain-query-language/dql-server/issues/47/comments","events_url":"https://api.github.com/repos/domain-query-language/dql-server/issues/47/events","html_url":"https://github.com/domain-query-language/dql-server/issues/47","id":154266474,"number":47,"title":"Problem: There is no conceptual architecture for DQL Server","user":{"login":"barryosull","id":325820,"avatar_url":"https://avatars.githubusercontent.com/u/325820?v=3","gravatar_id":"","url":"https://api.github.com/users/barryosull","html_url":"https://github.com/barryosull","followers_url":"https://api.github.com/users/barryosull/followers","following_url":"https://api.github.com/users/barryosull/following{/other_user}","gists_url":"https://api.github.com/users/barryosull/gists{/gist_id}","starred_url":"https://api.github.com/users/barryosull/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barryosull/subscriptions","organizations_url":"https://api.github.com/users/barryosull/orgs","repos_url":"https://api.github.com/users/barryosull/repos","events_url":"https://api.github.com/users/barryosull/events{/privacy}","received_events_url":"https://api.github.com/users/barryosull/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2016-05-11T15:03:48Z","updated_at":"2016-05-17T22:15:23Z","closed_at":null,"body":"Right now the architecture is purely conceptual, a lot of components of varying complexity, mashed together inside my head. It would be best if we had an overall view of everything, a high level diagram of the proposed solution. Would let us see everything in context.\r\n\r\nSolution: Create a high-level diagram showing the architecture of DQL server in terms of its components and how they interact\r\nSuccessCriteria: A link to the diagram is posted in this article, it doesn't have to be perfect, it's just a starting point."},"comment":{"url":"https://api.github.com/repos/domain-query-language/dql-server/issues/comments/219870640","html_url":"https://github.com/domain-query-language/dql-server/issues/47#issuecomment-219870640","issue_url":"https://api.github.com/repos/domain-query-language/dql-server/issues/47","id":219870640,"user":{"login":"barryosull","id":325820,"avatar_url":"https://avatars.githubusercontent.com/u/325820?v=3","gravatar_id":"","url":"https://api.github.com/users/barryosull","html_url":"https://github.com/barryosull","followers_url":"https://api.github.com/users/barryosull/followers","following_url":"https://api.github.com/users/barryosull/following{/other_user}","gists_url":"https://api.github.com/users/barryosull/gists{/gist_id}","starred_url":"https://api.github.com/users/barryosull/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barryosull/subscriptions","organizations_url":"https://api.github.com/users/barryosull/orgs","repos_url":"https://api.github.com/users/barryosull/repos","events_url":"https://api.github.com/users/barryosull/events{/privacy}","received_events_url":"https://api.github.com/users/barryosull/received_events","type":"User","site_admin":false},"created_at":"2016-05-17T22:15:23Z","updated_at":"2016-05-17T22:15:23Z","body":"Fourth iteration\r\n\r\n![dql command components 5](https://cloud.githubusercontent.com/assets/325820/15341119/d67a3f32-1c84-11e6-88d9-120fdb2a12c8.png)\r\n\r\n**Key changes:**\r\n- As per issue #68, an aggregate state store has been added, it is connected to the domain and nowhere else.\r\n- Made it clear that projections use databases for storing data, rather than inmemory\r\n- Restructured the diagram so that everything fit together better."}}