Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Memory-Centric Storage, Native Persistence, RDBMS Integration (CacheStore for RDBMS)
  • Key-Value APIs (NO JCache support)
  • SQL
  • Compute Grid
  • Service Grid
  • Machine Learning APIs
  • Advanced queries -scan, continuous
  • Transactions
  • Data Structures and Atomics
  • Ignite Messaging
  • Core Streaming APIs such as IgniteDataStreamer
  • Logging
  • Metrics and Tracing Framework
  • Command line tools and scripts such as Visor and control.sh
  • Standard (aka. thick clients) - Java, .Net, C++.
  • Spring Core - needed for configuration needs.

...

  • Spark Integration (to be discussed)
  • SpringData and SpringBoot
  • Kafka IntegrationService Grid
  • TensorFlow Integration
  • Cassandra Integration

...

Integration Name+1 (explain if needed)-1 (with explanation)
Twitter



ZeroMQ

Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody.

Alexey Kuznetsov 

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

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.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project)

Storm

Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

Alexey Zinoviev - all streaming tools/modules should be kept in one place (as part of AI or as Streaming AI separate project)

Flume

Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

Alexey Zinoviev - all ETL tools/modules should be kept in one place (as part of AI or as ETL AI separate project) I mean that Flume is tool for loading big datasets to AI

Flink

Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

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 an independent Github project that can be maintained by anybody.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Alexey Zinoviev

Pavel Kovalenko


Camel

Denis Magda - low usage, better to have as an independent Github project that can be maintained by anybody.

Alexey Kuznetsov

Alexey Goncharuk

Alexey Zinoviev

Pavel Kovalenko


Hibernate

Denis Magda - 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 Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

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 Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Pavel Kovalenko

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 Kuznetsov

Alexey Goncharuk Maybe drop it at all because moving this into a separate project may be a pain - a lot of internal API usages

Sergey Kozlov

Alexey Zinoviev 

Pavel Kovalenko


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 Goncharuk

Sergey Kozlov

Pavel Kovalenko

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

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.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Alexey Zinoviev

Pavel Kovalenko


YARN

Denis Magda - not sure it's useful any longer and should be supported by the community.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Alexey Zinoviev What was the purpose of this integration?

Pavel Kovalenko


Mesos

Denis Magda - not sure it's useful any longer and should be supported by the community.

Alexey Kuznetsov

Alexey Goncharuk

Sergey Kozlov

Alexey Zinoviev What was the purpose of this integration?

Pavel Kovalenko


.NET: Legacy Entity Framework and ASP.NET integrations

Denis Magda - outdated, needs to be replaced with a new one version.

Alexey Kuznetsov

Pavel Tupitsyn integrations with legacy technologies; also blocks .NET Core migration 

Sergey Kozlov

Alexey Zinoviev


Scalar

Alexey Goncharuk Not used, brings unnecessary dependency on scala, adds library conflicts

Sergey Kozlov

Alexey Zinoviev

Spark

Alexey Goncharuk Should be a separate project because it is a wrapper over the public API, but adds a scala dependency which slows down project compilation and complicates dependency management

Sergey Kozlov

Alexey Zinoviev I agree that it should be separate project, or we should integrate that with the Java API of SparkPavel Kovalenko Should be a separate project



The list of the integrations to be removed completely (don't even move them to an independent Github repo):

...