CodeDay

See the bottom of the page for completed contributions from thid year's RESTFEst Code Day

We'll be crowding around laptops, building clients, servers, middle-ware, and microservices all in the name of GETing some REST.

Focus on Service-Level Discovery on the Open Web

One of the most powerful aspects of the Web is that anyone can add a server anywhere anytime without asking for permission and others can start to link to that server from anywhere anytime without asking for permission. The Web was designed to allow free and open -- and instant access to a wide network of computers all over the world.

This has worked amazingly well for the world of documents and even for the world of Web-based applications. However, as we continue to grow the web of services the promise of "anything, anyone, anywhere, anytime" has not yet been fulfilled. Most API clients need to be purpose-built for using a single version of exsiting APIs -- that's a high bar for most people, even for many developers. This year, the plan is to explore the challenge of service-level discovery on the open web and what we can do to make it easier, faster, and more robust.

Open DISCO

After a short presentation/discussion on the challenge of service discovery on the Web, we'll start with a "strawman" proposal for a specification -- Discovering Interoperative Services for Continuous Operation (DISCO) (see spec here). We'll look at a demo server that implements DISCO and a sample API client that uses DISCO locate dependent services.

Code Day Projects

The plan is to identify projects that will help promote/improve this open DISCO idea and then form into teams to make progress on those projects for the day. Ideally, we'll 1) improve the written spec, 2) build better DISCO registry servers, 3) create DISCO-compatible client apps and, 4) raise the flag of easy service-level discovery on the Web.

Proposed Agenda

Morning

• Discussion/Presentation : The Challenge of Service-Level Discovery on the Open Web
• Short Demo of Open DISCO
• Project Planning (see possible project work below)
• BREAK
• Project Plan StandUp (teams announce projects)
• Project Work Begins

Lunch

Afternoon

• Project Status StandUp
• Project Work Continues
• Project Completion Demo/StandUp
• Discussion/Futures

Celebration

After the hard work, we'll all enjoy a Code Day Tea Bar/Crawl courtesy of our Code Day Sponsor Wiley

Possible Project Work for Code Day

• Clean up the DISCO Specification content
• Code an example DISCO Registry Server
• Code API clients that self-register w/ a DISCO server
• Code API clients that discovery dependent services using a DISCO server
• Write up possible extensions for the DISCO spec
  • Improved Search
  • Security
  • Federation
  • ????

Actual Project Work for Code Day 2019

Thanks to all for contributions to the DISCO spec and reference implementations for Code Day this year. Below is a (partial?) list of contributions demoed at the end of the day. Feel free to modify this list as needed. -- @mamund

• https://github.com/jhendley25/disco-on-rails - Reference DISCO registry on rails, WIP.
• https://github.com/imjohnbo/sea-of-tranquility-farmers-association and https://github.com/imjohnbo/lunar-veggie-farmer- @imjohnbo used Glitch to build a DISCO service that provides lunar vegetables. Contribute to imjohnbo/lunar-veggie-farmer
• https://github.com/FilmKnurd/disco_ex - Elixir Open DISCO server.
• https://open-disco.glitch.me/ and http://applicaster.github.io/siren-browser/#/siren-browser?url=https:%2F%2Fopen-disco.glitch.me
• https://github.com/open-disco/registry/pulls?q=is%3Apr+is%3Aclosed - Several updates to the reference server. home repo
• https://github.com/open-disco/open-disco-docs/issues/1 - Added open issue to explore Health-Checking feature of the DISCO server