Amila, It does not sound correct for a multi tenant system right? I think the solution should be making car deployment automatic @ the tenant creation level.
On Thu, Jun 23, 2016 at 11:52 AM, Amila Maha Arachchi <[email protected]> wrote: > All, > > Recently I learned following in a discussion about ESB-analytics. > > 1. We have to publish the data with tenant credentials (we also need the > analytics car deployed in all the tenants) > 2. A table per tenant is created > 3. There is one spark script which runs across all such tables and doing > the summarizing > 4. We have to take the user to a separate dashboard to present the stats > > Above looks fine when the tenant is supposed to have more control such as > running their own queries against the published data. > > But, when it comes to the cloud, we face issues with facilitating the > above. i.e. we need to deploy the car to all tenants. Since we dont need > the tenant credentials, we have to think of workarounds when publishing > data. Asking the tenant to configure them is not a option. > > Therefore, I would like to request the following flexibility. > > 1. We should allow to decide whether to publish data in super tenant mode > or tenant mode > 2. If its the ST mode, we deploy the car in ST space. > 3. Data gets published and stored in one table. i.e. no table per tenant > 4. Spark runs against that table > 5. Dashboard should be a SaaS app which filters data from the analyzed > table. > > Can above be facilitated? > > Regards, > Amila. > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
