On Thu, Nov 12, 2015 at 8:56 AM, Afkham Azeez <[email protected]> wrote:

> Yes, we have just been to KubeCon. Everybody is using YAML. Also, while
> looking at new libraries during research on MSS related stuff, all
> frameworks are using YAML now. Easy, minimal, lightweight config is where
> the world is today & XML is not the way to go. On a related note, minimal
> config or even better, zero config is what most people are moving towards.
>

This is a point I brought during my MS F/W comparison,  everybody moved or
moving to YAML today. IMO for new products such as MSS, GW we should use
YAML/JSON from the beginning.  Other advantage of YAML is we don't need
people to educate how to configure, use etc because people are already use
YAML for everyday works.

Thanks !

>
> On Wed, Nov 11, 2015 at 7:18 PM, Samisa Abeysinghe <[email protected]>
> wrote:
>
>>
>> On Thu, Nov 12, 2015 at 8:18 AM, Ramith Jayasinghe <[email protected]>
>> wrote:
>>
>>> are we going to take into account the whole migration effort ( for
>>> existing users) and the possible learning curve?
>>>
>>
>> ​There is no migration required. It is a new product major version and
>> new platform version. And we are talking about product configs not
>> artefacts
>> ​
>>
>>>
>>> I think we should review what exactly configurations we have (in each
>>> product) and how it will look in Yaml/Json? ( - and such a conversion would
>>> that lead to better user experience or just mess things up?)
>>>
>>>
>>> On Thu, Nov 12, 2015 at 5:37 AM, Thilina Piyasundara <[email protected]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> IMO its better to move out from XML. But Yaml and Json have its own
>>>> disadvantages as well. In yaml you can mess the hole thing if you miss a
>>>> single space/tab. In json you can't comment out a configuration block. Its
>>>> better to have a UI to configure and save those configs in a yaml or json
>>>> format specially when we have to deal with lots of configuration files.
>>>>
>>>> By the way, windows systems and python programs use a configuration
>>>> format called ini which is an old way of storing configurations using name
>>>> value pares with sections [1].
>>>>
>>>> 1. http://www.fcla.edu/z3950/everglades.html
>>>>
>>>> Thanks and regards,
>>>>
>>>> Thilina Piyasundara
>>>> Systems Engineer
>>>> ​
>>>> ​
>>>> Blog: thilina.piyasundara.org
>>>> Linkedin: linkedin.com/in/thilinapiyasundara
>>>>
>>>> WSO2, Inc.
>>>> ​
>>>> ​ <http://wso2.com/>
>>>> lean . enterprise . middleware
>>>> https://cloud.wso2.com
>>>>
>>>> On Tue, Nov 10, 2015 at 11:57 PM, Paul Fremantle <[email protected]> wrote:
>>>>
>>>>> I agree. I downloaded the MSS and C5 distros and I found the XML
>>>>> configs made them seem a little outdated.
>>>>>
>>>>> Paul
>>>>>
>>>>> On 10 November 2015 at 18:06, Afkham Azeez <[email protected]> wrote:
>>>>>
>>>>>> I brought up this idea a few years ago as well and it got shot down,
>>>>>> and I thought of bringing this back again. More and more, we are starting
>>>>>> to notice that the world is moving or has moved from verbose XML based
>>>>>> configuration to more concise YAML based configuration. So IMO, from C5
>>>>>> based products onwards we have to move to YAML based config.
>>>>>>
>>>>>> Thanks
>>>>>> Azeez
>>>>>>
>>>>>> --
>>>>>> *Afkham Azeez*
>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>> * <http://www.apache.org/>*
>>>>>> *email: **[email protected]* <[email protected]>
>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>>> *twitter: **http://twitter.com/afkham_azeez*
>>>>>> <http://twitter.com/afkham_azeez>
>>>>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>>>
>>>>>> *Lean . Enterprise . Middleware*
>>>>>>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Paul Fremantle
>>>>> Co-Founder, WSO2
>>>>>
>>>>> blog: http://pzf.fremantle.org
>>>>> twitter.com/pzfreo
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> E: [email protected]
>>> P: +94 777542851
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>*
> *email: **[email protected]* <[email protected]>
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*
> <http://twitter.com/afkham_azeez>
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
> *Lean . Enterprise . Middleware*
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;    http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to