Serialization is just one example, and it does not have to be XML.
JSON, YAML, HOCON configs are widely used.
Anyway, I see no reason for it NOT to be a POJO.
POJOs are ergonomic and work everywhere.
On Sun, Jul 11, 2021 at 8:24 AM Ivan Daschinsky wrote:
> > But configuration should be a POJO
But if you looked at other competitors, non of them doesn't use mutable
configurations. POJO or even more, JavaBeans are not used in the mos
products.
I just asked if you looked at others. Today it looks like you suggest use
just the same interfaces as in 2.x. Things changed a lot.
вс, 11 июл. 2
The main reason is that immutable configurations nowadays is more
preferable variant than mutable. For example, when you initialize client
you must copy configuration in order to be consistent. Nobody nowadays read
configuration from files as is, moreover -- the most microservices
retrieves just si
Ivan D, ok, you have convinced me.
Builder pattern is popular for this sort of thing, and not only in the Java
world.
Let's see if there are other opinions.
On Sun, Jul 11, 2021 at 6:59 PM Ivan Daschinsky wrote:
> The main reason is that immutable configurations nowadays is more
> preferable va
