Date: Friday January 8, 2pm EST (-5 UTC)

Meeting Goals

  1. Brainstorm ideas for development sprint

Attendees

Agenda

  1. Discuss Stefano Cossu's high-level architecture diagram, as announced on the fedora tech list
  2. Brainstorm activities for initial design/development sprints
    1. Service registration/discovery

Notes

  1. Initial design/development sprints. Sample patterns: Filtering pattern, Expose endpoints on resources, Service Discovery.
    1. Service discovery – some mechanism for common management of services. Important not to reinvent the wheel with service endpoints.
      1. There are existing patterns for distributed service discovery, e.g. ZooKeeper and Eureka
      2. Question: does the client interaction happen through a uniform API-X (management) endpoint or directly with services.
      3. Service Mediation could consist of data delivery (e.g. reverse proxy) or handoff to external service
      4. How does API-X relate to the Fedora3 disseminator architecture?
      5. Service Discovery seems to be a fundamental piece of API-X and should be a focus on early development
      6. Clients will need to use API-X to discover services: what will that look like, what standards will it use (consider how SOAP, WSDL and REST address this issue)?
      7. Unknown User (acoburn) and Daniel Davis will add some proof of concept sketches to the API-X wiki related to service discovery/registration in the next two weeks
  2. Stefano Cossu will add external services to his diagram, and it will be discussed in more depth on the next call

Next call

The next call is scheduled for 2pm ET on Friday, January 22

 

 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.