Re: [Architecture] Choosing APIs for implementing connectors

Hi Kausik, Good to hear that you are interested in doing connectors. Yes I guess you have a good combinations of apis. CRM, Accounting, Marketing and social media. I guess you can come up with an interesting bossiness use case :) On Mon, Jul 3, 2017 at 8:59 PM, Kausik

Re: [Architecture] wso2is-analytics 5.3.0 how store:// resolved to url ?

Tanya, Nipuna, Thank you! -- Regards, Dmitry --- Original message --- From: "Nipuna Chandradasa" Date: 3 July 2017, 07:37:00 Hi Tanya, Yes, you have to give the current host details of your server at [1]. So it will set the hostname to what you given on the config. 

[Architecture] Choosing APIs for implementing connectors

Hi All, We are planning to implement WSO2 ESB connectors for following APIs 1.Dotmailer 2.Sage 3.Streak 4.Buffer 5.Followupboss as a part of the 3rd year project for the course unit "Rapid Application Development". And also we will build a business scenario using these APIs. Can

Re: [Architecture] Unit-of-Work Pattern for Accessing/Modifying Claims in IdentityEventHandlers

+1. This will help to, 1. improve performance 2. Avoid trivial deadlocks. 3. Enforces Data consistency. Cheers, Ruwan On Mon, Jul 3, 2017 at 1:04 PM, Johann Nallathamby wrote: > Hi All, > > Currently the IdentityEventHandler architecture doesn't use any special > design

[Architecture] Unit-of-Work Pattern for Accessing/Modifying Claims in IdentityEventHandlers

Hi All, Currently the IdentityEventHandler architecture doesn't use any special design technique to access/modify (identity and non-identity) claims. Also each handler is self-contained and is expected to work independent from other handlers. Both of these reasons are causing performance issues

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

Hi Harsha, As discussed with Uvindra, after generating the API label for the composite API, it behaves same as other APIs regarding the gateway functionality. Since the Published APIs as well as the Composite APIs are published to the JMS topic, I thought of handling this in following way. *For