HI All,
I've opened an Ignite ticket with tasks description [1]
Is there anyone in Apache Ignite community who is interested in this
kind of work and will be able to complete it in the nearest couple of weeks?
[1] https://issues.apache.org/jira/browse/IGNITE-2448
Regards,
Denis
On 1/23/2016 11:28 AM, dma...@gridgain.com wrote:
Hi Eduardo,
It's nice to hear from you! Thanks the help and details!
Absolutely agree with you that the interface is straightforward and I
don't see any difficulties that can arise during its implementation.
I'll open an Apache Ignite JIRA ticket soon describing the integration
details and hope that someone from Ignite community will pick it up
the next week starting working on the plugin.
As per the hosting I would host everything on MyBatis GitHub repo as
it is already done for other plugins and in addition would add a
documentation to Apache Ignite [1]. This way both MyBatis and Ignite
community will be aware about the integration and we don't need to
host the plugin in different repos.
I've copied Ignite dev community to the discussion -
dev@ignite.apache.org. So please make sure that this dev list is
copied when you reply ;)
If someone else from either MyBatis or Ignite community has any
thoughts on this topic please share.
[1] https://apacheignite.readme.io
Regards,
Denis
On Saturday, January 23, 2016 at 12:46:08 AM UTC+3, Eduardo wrote:
Hi Denis,
First of all. Wellcome to the list!
AFAIK all the cache integration plugins have been developed by
ourselves. The interface is quite easy so the task is usualy
pretty straight forward.
I will be very happy to help with the integration! I would suggest
creating a new repo and work on it. Probably it will be better
that that someone from the Ignite project builds the plugin and we
provide information about how the interface works.
Regarding the future hosting, I suppose there will be no problem
in hosting the new project at our home in Github but is also
perfect that you host it as part of the ignite project. No problem
at all with any option!
Looking forward to starting! :)
2016-01-21 10:30 GMT+01:00 <dma...@gridgain.com <javascript:>>:
Hi MyBatis community!
I'm a committer and PMC of Apache Ignite [1] project and
writing to you on behalf of our community (+ CC-ed) to discuss
an integration between our projects that should be useful for
both sides.
In short, Apache Ignite is a high-performance, integrated and
distributed in-memory platform for computing and transacting
on large-scale data sets in real-time, orders of magnitude
faster than possible with traditional disk-based or flash
technologies.
Inside of our community we see a growing interest in a field
of usage MyBatis along with Apache Ignite. There are use cases
when developers/users wants to use Apache Ignite as MyBatis
second level cache. Since such an interest is growing
constantly we think that it's a right time to make this happen.
As I see MyBatis already supports second level cache for
Redis, Hazelcast and Ehcache.
How do you usually add such components? Were they added by
MyBatis guys or were developed by guys from Redis, Hazelcast,
etc.?
[1] https://ignite.apache.org/
Regards,
Denis
--
You received this message because you are subscribed to the
Google Groups "mybatis-user" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to mybatis-user...@googlegroups.com
<javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to a topic in the
Google Groups "mybatis-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/mybatis-user/CxSqG1dprm4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
mybatis-user+unsubscr...@googlegroups.com
<mailto:mybatis-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
