Re: [D] Support external and domain-specific code integrations [texera]

["xuang7 (via GitHub)" <gi...@apache.org>]

GitHub user xuang7 edited a discussion: Support external and domain-specific code integrations

Currently, some customized external or domain-specific code is maintained outside the core platform. Supporting these integrations in a consistent and maintainable way could reduce duplication, divergence, and additional maintenance overhead.

The challenge is that this code may appear in several forms:
- Locally modified third-party code: external code adapted primarily to access data on the platform; these changes may prevent the use of the originally published container images
- Standalone microservices: external or domain-specific services deployed alongside the main platform

These integrations are often implemented independently. Some resulting changes may be highly domain-specific and may not be necessary or broadly useful within the core platform.

One question is whether Texera should define a standard, documented API for external code and services to access platform-managed data, rather than relying on custom integration logic for each use case.

Feedback on how to support and manage these different types of external and domain-specific code would be very helpful. Please feel free to share any thoughts, concerns, or suggestions. Thank you!


GitHub link: https://github.com/apache/texera/discussions/6727

----
This is an automatically sent email for dev@texera.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@texera.apache.org