Hi All, Creating a reusable Store component was one of goals we had in our minds at UUF initial discussions. At that time there was couple of products APIM, AppM, EMM mobile store, GReg etc. that need a Store UI. So developing a generalized Store component was a requirement. However with the new product strategy there is not as many products (only APIM, IoT, IS) that need a Store UI. I feel like their requirements are too broad and diverse, hence we might not be able to develop a generalized Store component. Instead of developing a Store component, we can develop other small component that are needed for a store e.g. SSO component, Social, Self-signup, user-mgt. This is just my opinion/gut feeling. We should discuss this thoroughly.
Shall we setup a meeting for this? Thanks. On Tue, Sep 27, 2016 at 7:04 PM, Selvaratnam Uthaiyashankar < shan...@wso2.com> wrote: > > > On Tue, Sep 27, 2016 at 6:47 PM, Nuwan Dias <nuw...@wso2.com> wrote: > >> >> >> On Tue, Sep 27, 2016 at 6:31 PM, Selvaratnam Uthaiyashankar < >> shan...@wso2.com> wrote: >> >>> >>> On Tue, Sep 27, 2016 at 6:14 PM, Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> Do we really need a Store Framework for C5? >>>> >>> >>> >>> May be store framework is a wrong terminology, but there should be a >>> reusable store component written by using UUF. >>> >> >> So UUF itself is re-usable. We're going to build a Store component that's >> also re-usable using UUF. That's two levels of abstraction before we get to >> the actual generalization. It sounds like too much abstraction to me :). >> Unless there is a strong need, IMO we should just go by reusing what UUF >> offers and build our own Stores on that. >> > > I'll let UUF guys to answer this, but one of the requirement was to create > reusable components like store/login/dashboard using UUF. > > > >> >>> >>>> Rather, isn't it a UI framework (UUF) we need to build UIs? Apart from >>>> API-M and IoTS, are there any other products which need a Store? >>>> >>> >>> Store is needed in IS (end user portal, similar to AppM) as well. >>> >> >> The end user portal is a dashboard right? Its not really a Store. >> > > Part of end user portal is the store of applications available for the > user. Similar to app manager store with applications configured with SSO. > > > >> >>> >>> >>>> >>>> Even if we come up with a Store Framework, I think the facilities it >>>> provides will be minimal isn't it? Since the products that use this Store >>>> will have its own set of APIs for the back-end functionality, the only >>>> thing the Store UI would be doing is to call that set of APIs for the >>>> relevant functionality (ex: search API, list API). Therefore if we try to >>>> list the generic functionality offered by the Store Framework, I feel the >>>> functionality it provides will be minimal. And if that's true, then there's >>>> really no point in building a Store Framework. The products better build >>>> their own Stores using the common UI framework based on a theme that's >>>> common across the platform. >>>> >>>> On Tue, Sep 27, 2016 at 3:40 PM, Chandana Napagoda <chand...@wso2.com> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> While analyzing store requirements of C5 based products(IoT, APIM), we >>>>> have few areas to be clarified. Based on the current understanding, C5 >>>>> based store will not be bound into existing governance aspects. This >>>>> should >>>>> be a store framework with listing and searching capabilities. >>>>> >>>>> Should we consider generic metadata-based asset model for C5 based >>>>> Store? >>>>> >>>>> Does asset authoring(publisher) should be implemented with the store, >>>>> or relevant product team should implement it based on their use case? >>>>> >>>>> Does store needs to support multi-tenancy or are we moving to the >>>>> different tenant-based container approach? >>>>> >>>>> Regards, >>>>> Chandana >>>>> >>>>> -- >>>>> *Chandana Napagoda* >>>>> Associate Technical Lead >>>>> WSO2 Inc. - http://wso2.org >>>>> >>>>> *Email : chand...@wso2.com <chand...@wso2.com>**Mobile : >>>>> +94718169299 <%2B94718169299>* >>>>> >>>>> *Blog : http://cnapagoda.blogspot.com >>>>> <http://cnapagoda.blogspot.com> | http://chandana.napagoda.com >>>>> <http://chandana.napagoda.com>* >>>>> >>>>> *Linkedin : http://www.linkedin.com/in/chandananapagoda >>>>> <http://www.linkedin.com/in/chandananapagoda>* >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Architect - WSO2, Inc. http://wso2.com >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> S.Uthaiyashankar >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com/ - "lean . enterprise . middleware" >>> >>> Phone: +94 714897591 >>> >> >> >> >> -- >> Nuwan Dias >> >> Software Architect - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> > > > > -- > S.Uthaiyashankar > VP Engineering > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > -- Sajith Janaprasad Ariyarathna Software Engineer; WSO2, Inc.; http://wso2.com/ <https://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
