THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
| ID | IEP-36 | |||||||
| Author | Denis Magda | |||||||
| Sponsor | Denis Magda | |||||||
| Created |
| |||||||
| Status |
colour | Grey |
|
| Table of Contents |
|---|
Motivation
...
- Spark Integration (to be discussed)
- SpringData and SpringBoot
- Kafka Integration
- TensorFlow Integration
- Cassandra Integration
...
Below is a list of existing integrations that won't be turned into Ignite modules but rather would be moved to separate Github repositories and won't be maintained by Ignite community for every core release. If later the community sees demand for an unsupported integration, it can be taken back and be officially supported (testing, dev, releases, compatibility with the core) as an Ignite module.
The list of integrations that to be moved to independent Github repositories and will not be supported by the community for every Ignite release:
We discussed in dev list[1] and agreed on creating a new repository for hosting our Ignite integrations.
As discussed [2] with respect to releases all the extensions need to be verified for an upcoming release and updated if needed (with the version increase only for those updated)
The list of integrations that to be moved to independent Github repositories and will not be supported by the community for every Ignite release:
| Integration Name | +1 (explain if needed) | -1 (with explanation) | ||
|---|---|---|---|---|
| Kafka | ||||
Denis Magda - that's a side project for apps that use Twitter | ||||
| Integration Name | +1 (explain if needed) | -1 (with explanation) | Denis Magda - that's a side project for apps that use Twitter. | |
| ZeroMQ | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project) | ||
| RocketMQ | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | |||
| ZeroMQ | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project) | ||
| StormRocketMQ | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project) | ||
| FlumeStorm | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all ETL streaming tools/modules should be kept in one place (as part of AI or as ETL Streaming AI separate project) I mean that Flume is tool for loading big datasets to AI | ||
| FlumeFlink | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming ETL tools/modules should be kept in one place (as part of AI or as Streaming ETL AI separate project) I mean that Flume is tool for loading big datasets to AI | ||
| FlinkMQTT | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project) | ||
| MQTT | Denis Magda - low usage, better to have as | Camel | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | |
| HibernateCamel | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | |||
| Hibernate | Denis Magda - Spring Data gets much bigger adoption for Ignite deployments. Don Spring Data gets much bigger adoption for Ignite deployments. Don't see a lot of traction with Hibernate. It's hard to maintain it in various variations - Ignite goes with several modules of different versions. Better to have as an independent Github project with forks for specific Hibernate versions. | Alexey Zinoviev - I suppose it's useful feature for wide adoption among Java Devs who use AI not like cache, but like database | ||
| JMS | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. | Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project). Also, I didn't see the Kafka Integration in this list | ||
| AOP-Based Grid | Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody. Alexey Goncharuk Maybe drop it at all because moving this into a separate project may be a pain - a lot of internal API usages | |||
| JSR-107(JCache) | Denis Magda - don't see any value in supporting this JSR rather than claiming that specification. It's better to have much cleaner Ignite key-value API without any dependencies influenced by the specification. | Alexey Zinoviev we should ask about that question the user-community, I have heard many times that that the JCache implementation is important for Java Devs Ivan Pavlukhin It is quite natural for me to imagine integration with Ignite using some kind of standard API. The situation with JCache is similar to JDBC. AFAIR Spring has a JCache integration. If we are going to evolve caching trait then we should support easy integartion with Spring. If there alternatives to JCache then we should consider them. | ||
| OSGi | Denis Magda - this integration is already broken and badly maintained. Haven't come across anybody who uses OSGi in the projects Ignite is targeted for. | |||
| YARN | Denis Magda - not sure it's useful any longer and should be supported by the community. Alexey Zinoviev What was the purpose of this integration? | |||
| Mesos | Denis Magda - not sure it's useful any longer and should be supported by the community. Alexey Zinoviev What was the purpose of this integration? | |||
.NET: Legacy Entity Framework and ASP.NET integrations | Denis Magda - outdated, needs to be replaced with a new one version. Pavel Tupitsyn integrations with legacy technologies; also blocks .NET Core migration | |||
| Scalar | Alexey Goncharuk Not used, brings unnecessary dependency on scala, adds library conflicts |
...
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Modularization-td42486.html
Reference Links
This initiative is also related to the discussion of Apache Ignite APIs update/removal - Apache Ignite 3.0 Wishlist
Tickets
Reference Links
This initiative is also related to the discussion of Apache Ignite APIs update/removal - Apache Ignite 3.0 Wishlist
Tickets
// Links or report with relevant JIRA tickets.Jira server ASF JIRA columnIds issuekey,summary,issuetype,updated,assignee,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution columns key,summary,type,updated,assignee,Priority,Priority,Priority,Priority,priority,status,resolution maximumIssues 20 jqlQuery project = Ignite AND labels IN (iep-36) order by key serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
Overview
Content Tools
Apps