Yes, we will follow the metadata issue after config and registry issues done.

At 2020-02-08 11:31:38, "zhaojun" <[email protected]> wrote:
>sure, kim and haoran will follow the metadata issue in future
>
>------------------
>Zhao Jun (cherrylzhao)
>Apache ShardingSphere & ServiceComb
>
>> On Feb 8, 2020, at 10:59 AM, guangyuan wang <[email protected]> wrote:
>> 
>> 4. Design Metadata model, integrate with Config and Registry.
>> Zhaojun has mentioned this before, did he discuss with you?
>> 
>> 秦金卫 <[email protected]> 于2020年2月6日周四 下午9:17写道:
>> 
>>> Hello, Nicholas:
>>>   We will provide every specified design document for each phase, and
>>> send a mail to invite community members, join in and discuss about the
>>> certain topic.
>>> At 2020-02-06 19:41:17, "蒋晓峰" <[email protected]> wrote:
>>>> Hi, Haoran Meng:
>>>>   Could you please provide the design document of "upgrade the
>>>> Orchestration module to the Governance module"? And please put the
>>> document
>>>> into confluence of wiki to let community developer for reference.
>>>> 
>>>> Thanks,
>>>> Nicholas Jiang
>>>> 
>>>> On Thu, Feb 6, 2020 at 4:18 PM Haoran Meng <[email protected]>
>>> wrote:
>>>> 
>>>>> Hello everyone, we plan to optimize Orchestration of Apache
>>>>> ShardingSphere(incubator),
>>>>> 
>>>>> and we plan to upgrade the Orchestration module to the Governance
>>> module.
>>>>> 
>>>>> The goal is to package Governance as a core component of distributed
>>>>> database HA.
>>>>> 
>>>>> Here are our plans:
>>>>> 
>>>>>   1.
>>>>> 
>>>>>   Sort out and redesign ConfigCenter and RegistryCenter, and separate
>>> them
>>>>>   from specific domain models, so that developers can easily integrate
>>> and
>>>>>   implement data access and change notification functions based on a
>>>>> certain
>>>>>   technology.
>>>>>   2.
>>>>> 
>>>>>   Consider the functions of Distributed Lock and Leaf ID Generator,
>>> keep
>>>>>   or integrate third party?
>>>>>   3.
>>>>> 
>>>>>   Provide API and SPI related to the above designs, which requires
>>> clear
>>>>>   and Least Knowledge Principle.
>>>>>   4.
>>>>> 
>>>>>   Design Metadata model, integrate with Config and Registry.
>>>>>   5.
>>>>> 
>>>>>   Design the management of JDBC and Proxy nodes, the detection and
>>>>>   reconstruction mechanism after nodes crashed.
>>>>>   6.
>>>>> 
>>>>>   Design the elegant Refresh mechanism of Connection and the processing
>>>>>   under the multi-threaded Executor. Minimize the reconstruction of all
>>>>>   internal and external resource objects.
>>>>>   7.
>>>>> 
>>>>>   Design the model and synchronization mechanism of Rules and
>>> DataSources.
>>>>>   8.
>>>>> 
>>>>>   Spring NameSpace, Spring Boot integration.
>>>>>   9.
>>>>> 
>>>>>   Governance module integrates with JDBC and Proxy modules to achieve
>>> HA.
>>>>> 
>>>>> Everyone is welcome to actively discuss and provide comments and
>>>>> suggestions.
>>>>> 
>>> 
>

Reply via email to