+1 for the approach. Don't we need to consider the domain model for the whole application, rather than component-wise? Because, some of the attributes are updated from different components. In this diagram Cluster object has cluster id only
On Wed, Jun 24, 2015 at 11:09 AM, Imesh Gunaratne <im...@apache.org> wrote: > Thanks for looking into this Jane! May be we can maintain MySQL Workbench > ER Models in our source repository as it provides features for generating > SQL scripts. > > You should be able to continue this effort in a new branch and send pull > requests as you progress. Please note that we also need to update the > embedded H2 database with this. > > Thanks > > On Wed, Jun 24, 2015 at 10:57 AM, Jane Mariathas <j...@wso2.com> wrote: > >> Hi , >> >> In Stratos there are components called StratosManager , CloudController, >> AutoScaller which has there own registry and the data stored as serialized >> object, which is not an easy way to manage the data. >> >> So after an offline discussion with Imesh we decided to persist the data >> in the database as an object without serializing which is good way to >> manage the data. >> >> I would like to contribute to this issue. I have started with the >> StratosManager Component and created the ER model. >> >> I have attached the ER Model and the ER diagram for the StratosManger >> Component. >> Any feedback on this would be helpful >> >> Thanks, >> >> -- >> Jane Aarthy Mariathas >> *Intern*,Software Engineering >> j...@wso2.com >> > > > > -- > Imesh Gunaratne > > Senior Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Sajith Kariyawasam *Committer and PMC member, Apache Stratos, * *WSO2 Inc.; http://wso2.com <http://wso2.com>* *Mobile: 0772269575*
