Connector service vs connector webservice? about enterprise-search-sharepoint-server-connector HOT 3 CLOSED

Sure thing - it really boils to the preference to push information out of the network vs having it be pulled.

To me the big benefit of self hosted connectors is the way we can use them to avoid dealing with restrictions on corporate networks. With the push architecture we only need outgoing ports (which barely even needs to be discussed with the networking team), but if we need to serve data over HTTPS which can be read by a service on the internet it becomes a more involved conversation.

I've just added my email to my profile if you want to get in touch

from enterprise-search-sharepoint-server-connector.

@catmanjan great question and excellent observation. The elastic/connectors repo is built on a new connector framework that is technical preview. As you noted, this is built on a new architecture. We absolutely would like to standardize on an approach, and are waiting to see the customer feedback on the preview for that variation of the framework. Are you interested in chatting with me (I'm the product manager for this initiative) to walk me through the changes you would need to do in your server design based on either of these architectures? It would be fantastic to be able to get your feedback to make sure we're making the right choices for customers like yourself.

from enterprise-search-sharepoint-server-connector.

I'll send you an email right now to set up some time!

from enterprise-search-sharepoint-server-connector.