You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Oliver B. Fischer" <o....@swe-blog.net> on 2016/04/22 18:52:23 UTC
Features I miss in configuration framework
Hi,
let me explain the background of the following feature requests before I
describe them.
Currently I work in a team which is responsible for quite a lot of
services - I will avoid the term microservices ;-) One problem is the
configuration and the maintenance of all the different properties.
Sometime we can not be sure if we can remove a property or not. How
should we know if a property is still used or so much the worse a
property is missing.
Especially in legacy environments we sometimes have some properties we
don't know and what they are used for.
Both problems can be solved but it takes time.
This is the moment there Tamaya comes in. I would like to see the
following features in Tamaya.
1. Statistics: It should be possible to retrieve some statistics for a
given property. I would like to "ask" Tamaya how often a property has
been requested.
2. Inline documentation: It should be possible to add a simple comment
to a property as description of the property. The description should be
available via the API.
What do you think about theses possible features? Would they be helpfull
even for you?
Bye,
Oliver
<http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on>
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Features I miss in configuration framework
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Hi Werner,
of course. And we should try to invite Anatole. The JUG meeting will
start at 7 PM and I think it will take 1 1/2 hours. Should we meet
before or after the meeting? Or during the meeting, which could be
dificult as some of us will take part in the panel discussion.
WDYT?
Oliver
Am 22.04.16 um 18:57 schrieb Werner Keil:
> Hi Oliver,
>
> Thanks for the suggestion. Since at least myself, Otavio/Bruno from SouJava
> and other EC members (e.g. CDI Spec Lead Red Hat) who probably have an
> interest in this will meet you in Berlin at the JUG meeting, maybe we have
> a chance to discuss it there. Either under the category of "Next JSRs"
> which the EC already brushed in earlier meetings or specific to Tamaya. If
> it's not too early there (after 7pm CET should be OK though) or he's busy
> with his Tamaya talk, maybe we could even invite Anatole to a Hangout then?
>
> Cheers,
> Werner
>
>
> On Fri, Apr 22, 2016 at 6:52 PM, Oliver B. Fischer <o.b.fischer@swe-blog.net
>> wrote:
>> Hi,
>>
>> let me explain the background of the following feature requests before I
>> describe them.
>>
>> Currently I work in a team which is responsible for quite a lot of
>> services - I will avoid the term microservices ;-) One problem is the
>> configuration and the maintenance of all the different properties.
>> Sometime we can not be sure if we can remove a property or not. How should
>> we know if a property is still used or so much the worse a property is
>> missing.
>>
>> Especially in legacy environments we sometimes have some properties we
>> don't know and what they are used for.
>>
>> Both problems can be solved but it takes time.
>>
>> This is the moment there Tamaya comes in. I would like to see the
>> following features in Tamaya.
>>
>> 1. Statistics: It should be possible to retrieve some statistics for a
>> given property. I would like to "ask" Tamaya how often a property has been
>> requested.
>>
>> 2. Inline documentation: It should be possible to add a simple comment to
>> a property as description of the property. The description should be
>> available via the API.
>>
>> What do you think about theses possible features? Would they be helpfull
>> even for you?
>>
>> Bye,
>>
>> Oliver
>>
>>
>> <
>> http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on>
>>
>>
>> --
>> N Oliver B. Fischer
>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fischer@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fischer@jabber.org
>> X http://xing.to/obf
>>
>>
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Features I miss in configuration framework
Posted by Werner Keil <we...@gmail.com>.
Hi Oliver,
Thanks for the suggestion. Since at least myself, Otavio/Bruno from SouJava
and other EC members (e.g. CDI Spec Lead Red Hat) who probably have an
interest in this will meet you in Berlin at the JUG meeting, maybe we have
a chance to discuss it there. Either under the category of "Next JSRs"
which the EC already brushed in earlier meetings or specific to Tamaya. If
it's not too early there (after 7pm CET should be OK though) or he's busy
with his Tamaya talk, maybe we could even invite Anatole to a Hangout then?
Cheers,
Werner
On Fri, Apr 22, 2016 at 6:52 PM, Oliver B. Fischer <o.b.fischer@swe-blog.net
> wrote:
> Hi,
>
> let me explain the background of the following feature requests before I
> describe them.
>
> Currently I work in a team which is responsible for quite a lot of
> services - I will avoid the term microservices ;-) One problem is the
> configuration and the maintenance of all the different properties.
> Sometime we can not be sure if we can remove a property or not. How should
> we know if a property is still used or so much the worse a property is
> missing.
>
> Especially in legacy environments we sometimes have some properties we
> don't know and what they are used for.
>
> Both problems can be solved but it takes time.
>
> This is the moment there Tamaya comes in. I would like to see the
> following features in Tamaya.
>
> 1. Statistics: It should be possible to retrieve some statistics for a
> given property. I would like to "ask" Tamaya how often a property has been
> requested.
>
> 2. Inline documentation: It should be possible to add a simple comment to
> a property as description of the property. The description should be
> available via the API.
>
> What do you think about theses possible features? Would they be helpfull
> even for you?
>
> Bye,
>
> Oliver
>
>
> <
> http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on>
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
>
Re: Features I miss in configuration framework
Posted by Anatole Tresch <at...@gmail.com>.
Hi all
some similar features are already there/started:
- using the model module and injection the injection points are
autodocumenting.
- Metrics can be easily provided and added to the model module by adding an
additional filter, which is aware of any property read.
- Configuration models also allow to validat configuration and provide
descriptions.
Sounds good? I will definitivly also add UI support for the model part, so
we get some kind of autoconfiguration and validation + metrics relatively
easily. Nice thing is also, we can show these features quite good ;)
Nevertheless we should check the functionality in the model part, to see
how good it matches and if there are options to simplify its use even more.
Everybody is welcome to help here.
Overall I currently see three major features for the next release (maybe
even 2 and let one over the over-next one):
- having a UI part that gives visualization of the Tamaya system and its
ocnfiguration, including the possibility to edit config.
- further ellaborate on the documentation and metrics feature, creating
benefits also for integration of Tamaya in existing projects.
- Adding a simple configuration mechanism to configure Tamaya descriptivly
(in logging we have logging.xml, if we can provide a similar simple
mechanism it would be a blast).
So this matches quite good also your ideas/reqs....
J Anatole
2016-04-22 19:04 GMT+02:00 John D. Ament <jo...@apache.org>:
> I'm wondering if this is a use case for Tamaya Server? Or would you expect
> it inline when reading configuration (e.g. yaml or json). I don't think
> the properties syntax would help much here.
>
> Basically, I share your concerns. Right now, to achieve the documentation
> piece my team maintains a large confluence page with all of the
> configuration settings, the defaults, description of where used. Its very
> useful, but hard to follow.
>
> Metrics is less of a concern, since we cache configuration on start up
> rather than at runtime.
>
> John
>
> On Fri, Apr 22, 2016 at 12:52 PM Oliver B. Fischer <
> o.b.fischer@swe-blog.net>
> wrote:
>
> > Hi,
> >
> > let me explain the background of the following feature requests before I
> > describe them.
> >
> > Currently I work in a team which is responsible for quite a lot of
> > services - I will avoid the term microservices ;-) One problem is the
> > configuration and the maintenance of all the different properties.
> > Sometime we can not be sure if we can remove a property or not. How
> > should we know if a property is still used or so much the worse a
> > property is missing.
> >
> > Especially in legacy environments we sometimes have some properties we
> > don't know and what they are used for.
> >
> > Both problems can be solved but it takes time.
> >
> > This is the moment there Tamaya comes in. I would like to see the
> > following features in Tamaya.
> >
> > 1. Statistics: It should be possible to retrieve some statistics for a
> > given property. I would like to "ask" Tamaya how often a property has
> > been requested.
> >
> > 2. Inline documentation: It should be possible to add a simple comment
> > to a property as description of the property. The description should be
> > available via the API.
> >
> > What do you think about theses possible features? Would they be helpfull
> > even for you?
> >
> > Bye,
> >
> > Oliver
> >
> >
> > <
> >
> http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on
> > >
> >
> >
> > --
> > N Oliver B. Fischer
> > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> > P +49 30 44793251
> > M +49 178 7903538
> > E o.b.fischer@swe-blog.net
> > S oliver.b.fischer
> > J oliver.b.fischer@jabber.org
> > X http://xing.to/obf
> >
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*Blogs: **http://maketechsimple.wordpress.com
<http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks*
Re: Features I miss in configuration framework
Posted by "John D. Ament" <jo...@apache.org>.
I'm wondering if this is a use case for Tamaya Server? Or would you expect
it inline when reading configuration (e.g. yaml or json). I don't think
the properties syntax would help much here.
Basically, I share your concerns. Right now, to achieve the documentation
piece my team maintains a large confluence page with all of the
configuration settings, the defaults, description of where used. Its very
useful, but hard to follow.
Metrics is less of a concern, since we cache configuration on start up
rather than at runtime.
John
On Fri, Apr 22, 2016 at 12:52 PM Oliver B. Fischer <o....@swe-blog.net>
wrote:
> Hi,
>
> let me explain the background of the following feature requests before I
> describe them.
>
> Currently I work in a team which is responsible for quite a lot of
> services - I will avoid the term microservices ;-) One problem is the
> configuration and the maintenance of all the different properties.
> Sometime we can not be sure if we can remove a property or not. How
> should we know if a property is still used or so much the worse a
> property is missing.
>
> Especially in legacy environments we sometimes have some properties we
> don't know and what they are used for.
>
> Both problems can be solved but it takes time.
>
> This is the moment there Tamaya comes in. I would like to see the
> following features in Tamaya.
>
> 1. Statistics: It should be possible to retrieve some statistics for a
> given property. I would like to "ask" Tamaya how often a property has
> been requested.
>
> 2. Inline documentation: It should be possible to add a simple comment
> to a property as description of the property. The description should be
> available via the API.
>
> What do you think about theses possible features? Would they be helpfull
> even for you?
>
> Bye,
>
> Oliver
>
>
> <
> http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on
> >
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
>