Idiomatic way of configuring caches on client

[Alexey Kuznetsov-2]

I'm working on Ignite Web Console.
And this utility is generating XML and java code with cluster configuration.

For server-side I generate XML and java code that describe caches.

But should I do the same when generating client node configuration?

I think that I should only generate NearCacheConfiguration in case
of client node
and do not generate CacheConfiguration in XML and java.

Also, it is a good idea to generate NearCacheConfiguration for each cache
by default?
Or better to give a choice of caches?


Thoughts?

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[yzhdanov]

I think it is very good idea to generate client node config as well and it
seems that console should provide ability to configure near cache (e.g.
start size and eviction policy) or turn it off completely.

--Yakov

2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov <[hidden email]>:

> I'm working on Ignite Web Console.
> And this utility is generating XML and java code with cluster
> configuration.
>
> For server-side I generate XML and java code that describe caches.
>
> But should I do the same when generating client node configuration?
>
> I think that I should only generate NearCacheConfiguration in case
> of client node
> and do not generate CacheConfiguration in XML and java.
>
> Also, it is a good idea to generate NearCacheConfiguration for each cache
> by default?
> Or better to give a choice of caches?
>
>
> Thoughts?
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[Alexey Goncharuk]

I see nothing wrong with generating a server config for a client node. This
may be used in a case when server nodes are started with plain empty config
and clients are deploying caches to the grid.

[Alexey Kuznetsov-2]

Yakov, Ignite console has UI (on Summary page) for near cache configuration
with optional eviction policy.

On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov <[hidden email]> wrote:

> I think it is very good idea to generate client node config as well and it
> seems that console should provide ability to configure near cache (e.g.
> start size and eviction policy) or turn it off completely.
>
> --Yakov
>
> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
>
> > I'm working on Ignite Web Console.
> > And this utility is generating XML and java code with cluster
> > configuration.
> >
> > For server-side I generate XML and java code that describe caches.
> >
> > But should I do the same when generating client node configuration?
> >
> > I think that I should only generate NearCacheConfiguration in case
> > of client node
> > and do not generate CacheConfiguration in XML and java.
> >
> > Also, it is a good idea to generate NearCacheConfiguration for each cache
> > by default?
> > Or better to give a choice of caches?
> >
> >
> > Thoughts?
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[Alexey Kuznetsov-2]

Alex,

Thanks for your suggestions. We will generate server cache configs + client
near cache configs.

On Wed, Dec 9, 2015 at 9:06 PM, Alexey Kuznetsov <[hidden email]>
wrote:

> Yakov, Ignite console has UI (on Summary page) for near cache
> configuration with optional eviction policy.
>
> On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov <[hidden email]> wrote:
>
>> I think it is very good idea to generate client node config as well and it
>> seems that console should provide ability to configure near cache (e.g.
>> start size and eviction policy) or turn it off completely.
>>
>> --Yakov
>>
>> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
>>
>> > I'm working on Ignite Web Console.
>> > And this utility is generating XML and java code with cluster
>> > configuration.
>> >
>> > For server-side I generate XML and java code that describe caches.
>> >
>> > But should I do the same when generating client node configuration?
>> >
>> > I think that I should only generate NearCacheConfiguration in case
>> > of client node
>> > and do not generate CacheConfiguration in XML and java.
>> >
>> > Also, it is a good idea to generate NearCacheConfiguration for each
>> cache
>> > by default?
>> > Or better to give a choice of caches?
>> >
>> >
>> > Thoughts?
>> >
>> > --
>> > Alexey Kuznetsov
>> > GridGain Systems
>> > www.gridgain.com
>> >
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[dsetrakyan]

On Wed, Dec 9, 2015 at 6:07 AM, Alexey Kuznetsov <[hidden email]>
wrote:

> Alex,
>
> Thanks for your suggestions. We will generate server cache configs + client
> near cache configs.
>

Sounds good. Let’s make sure we name them properly, so users will clearly
understand which one is for what.

>
> On Wed, Dec 9, 2015 at 9:06 PM, Alexey Kuznetsov <[hidden email]>
> wrote:
>
> > Yakov, Ignite console has UI (on Summary page) for near cache
> > configuration with optional eviction policy.
> >
> > On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov <[hidden email]>
> wrote:
> >
> >> I think it is very good idea to generate client node config as well and
> it
> >> seems that console should provide ability to configure near cache (e.g.
> >> start size and eviction policy) or turn it off completely.
> >>
> >> --Yakov
> >>
> >> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
> >>
> >> > I'm working on Ignite Web Console.
> >> > And this utility is generating XML and java code with cluster
> >> > configuration.
> >> >
> >> > For server-side I generate XML and java code that describe caches.
> >> >
> >> > But should I do the same when generating client node configuration?
> >> >
> >> > I think that I should only generate NearCacheConfiguration in case
> >> > of client node
> >> > and do not generate CacheConfiguration in XML and java.
> >> >
> >> > Also, it is a good idea to generate NearCacheConfiguration for each
> >> cache
> >> > by default?
> >> > Or better to give a choice of caches?
> >> >
> >> >
> >> > Thoughts?
> >> >
> >> > --
> >> > Alexey Kuznetsov
> >> > GridGain Systems
> >> > www.gridgain.com
> >> >
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>