On Tue, May 29, 2018 at 8:03 PM, Ruwan Abeykoon <[email protected]> wrote:
> Hi Pulasthi, > I would vote for removing siddhi from IS 5.6.0. Reasons, > 1. Siddni is used for demonstrating advanced Adaptive Authentication. For > this purpose, siddhi embedded engine is not suitable anyway. > 2. It adds considerable memory footprint and delays startup. > 3. There may be classloader incompatibilities, in different JVM, > I'm the one who originally suggest to have Siddhi profile but after getting opinions from Prabath and Ruwan I also +1 remove Siddhi profile, this mean we should support SP4 for both evaluation and production cases. Thanks ! > > Cheers, > Ruwan > > On Tue, May 29, 2018 at 6:09 PM, Pulasthi Mahawithana <[email protected]> > wrote: > >> Hi All, >> >> We had few profiles in IS as below, >> >> - Default - Profile that had all the identity backend + identity UI + >> BPS + siddhi features (since IS 5.6.0 milestone releases) >> - IS - Profile that had identity backend and identity UI features >> - Workflow - bps and features and its dependencies >> - Worker - Identity backend features >> >> By default, the server was starting in the default profile which >> activates bps and siddhi runtimes. However, these runtimes were not >> recommended in production. They were only included for trying out the >> related features OOTB without having to go for an external server. In >> production systems, our recommendation was to use separate external servers >> (BPS/EI for workflows and DAS for analytics) if those features are >> required. >> >> Due to above reason, we have decided to change the profiles as below. >> >> - Default - Identity backend and UI features only (Same as previous >> 'IS' profile) >> - Full - All Identity features + BPS + Siddhi (Same as previous >> 'Default' profile) >> - Worker - Identity backend features (unchanged) >> - Workflow - BPS features and dependencies (unchanged) >> >> Since the server now starts with Identity features only, this can be >> directly used in production without any overhead due to additional feature >> activation or profile changes. >> >> If any user wants to try out any workflows or analytic related features, >> that user will need to start the server in 'full' profile with >> '-Dprofile=full' argument. >> >> Please let us know of any concerns. >> -- >> *Pulasthi Mahawithana* >> Associate Technical Lead >> WSO2 Inc., http://wso2.com/ >> Mobile: +94-71-5179022 >> Blog: https://medium.com/@pulasthi7/ >> >> <https://wso2.com/signature> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Ruwan Abeykoon* > *Associate Director/Architect**,* > *WSO2, Inc. http://wso2.com <https://wso2.com/signature> * > *lean.enterprise.middleware.* > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sagara Gunathunga Director; WSO2, Inc.; http://wso2.com Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com Mobile : +9471 <+94%2071%20565%209887>2149951
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
