[Architecture] [Announce] WSO2 Enterprise Integrator 6.1.1-update19 Released !

Hi All, The WSO2 Integration team is pleased to announce the release of Enterprise Integrator 6.1.1-update19. It is available for download from here *Tasks/Bug Fixes and Improvements* -

Re: [Architecture] [MB] MQTT : support around 100K mqtt connections using WSO2 MB

Hi Youcef, WSO2 Message broker has a thread pool with threads working to push messages from DB to subscribers. Thus if we create x number of connections to a broker those x number of connections will be distributed across the threads in the pool. We use LMax Disruptor [1] to batch incoming

Re: [Architecture] [GDPR] API Manager 3.0.0 GDPR Support

Hi all, When this is done up to some extent let's have a code review. I'm still struggling to understand the difference between user_id and pseudo name. And wondering whether we actually need a user_id concept if we implement something based on a pseudo name or vice versa. Just to be clear on

[Architecture] [Puppet] WSO2 Puppet Common v1.1.0 and Puppet Base v1.2.0 Released!

Hi Folks, We are pleased to release WSO2 Puppet Common v1.1.0 and Puppet Base v1.2.0 with following improvements and fixes to the code base. *WSO2 Puppet Common v1.1.0 Release* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Re: [Architecture] [MB] MQTT : support around 100K mqtt connections using WSO2 MB

Hi Imesh, Thank you very much. I must present the solutions to the architectural committee of Tuesday, 06/02/2018. It's good to have some information even this weekend on my work email. Thanks Youcef HILEM -- Sent from:

[Architecture] WSO2 API Manager 2.1.0-update9 Released !

The WSO2 API Manager team is pleased to announce the release of version 2.1.0-update9 of API Manager. WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of API management challenges such as API

Re: [Architecture] [GDPR] API Manager 3.0.0 GDPR Support

Yes what you are suggesting is valid scenario. That is why GDPR talks about time to effect user data deletion. In this particular scenario if we need to maintain data for 6 months then we can remove mapping after 6 months. Or we can completely disable GDPR like i mentioned early. Thanks,

Re: [Architecture] [GDPR] API Manager 3.0.0 GDPR Support

Hi Sanjeewa, So, if we are storing with the pseudo name and if we remove the mapping, the audit logs won't have any value would it? For e.g, a banking application/mobile, would want to hold the audit logs for at least 6 months - 1 year for audit purposes/legal purposes but would want to delete

Re: [Architecture] [IAM] UX design for Retryable Outbound Provisioning Feature.

Hi Imesh, Thank you very much for the suggestions. Please find my comments inline. Hi Menaka, >>> >>> Please find the bellow suggestions. >>> >>> IMHO, the filtration controls should resemble a visual connection to the >>> listing. >>> >> I have followed the default UX design in Management

Re: [Architecture] [GDPR] API Manager 3.0.0 GDPR Support

Hi Sanjeewa, Do we have to remove the entries from the log files as well? even audit logs? does this mean we will remove from archived logs as well? If so, shouldn't this be a decision of the data controller? With this design, they have no control over the logs only right? On Fri, Feb 2, 2018