Versions Compared

Old Version 6

changes.mady.by.user Barbara Pruijn

Saved on

compared with

New Version 7

changes.mady.by.user Barbara Pruijn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

  • Problem Statement
  • User Goals
  • Product Goals
  • Risks and Mitigations
  • Project Milestones

    •  

     

                                                                     DRAFT VERSION

    Summary

    In order to make Geode more extendable, provide a public API to the Cluster Configuration Service to allow other extensions to save configuration settings.

    Problem Statement

    Currently, developers working on different parts of the code need to use internal APIs to implement saving configuration settings to the Cluster Configuration service.

    User Goals

    Create a more modular product to allow for easy extension and integration. The beneficiaries of this work are the developers working on different parts of the code such as Queries for Lucene index, storage for the JDBC connector, other Geode developers and anyone who wants to save settings to the Cluster Configuration Service.


    Product Goals
    The developer should be able to save their configuration to the Cluster Configuration Service without having to restart the servers.

    Obtain the cluster config service from cache.

    Pass config object to the cluster config service.

    CRUD operations support for config objects.


    Risks and Mitigations
    This could be a slippery slope for scope creep regarding modularization of Geode. It is important to think small but yet modular.

    Project Milestones
    Milestone for this project are implementation an extension to the new Public API.