Skip to content

Add OfficeFloor to REST Frameworks#1281

Open
sagenschneider wants to merge 1 commit into
akullpp:masterfrom
officefloor:master
Open

Add OfficeFloor to REST Frameworks#1281
sagenschneider wants to merge 1 commit into
akullpp:masterfrom
officefloor:master

Conversation

@sagenschneider

@sagenschneider sagenschneider commented Jul 5, 2026

Copy link
Copy Markdown

This adds OfficeFloor under REST Frameworks.

Disclosure: I'm the author of OfficeFloor, so this is a self-submission. I've tried to justify it against the contribution criteria below rather than on my own opinion of the project.

What it is: a Spring Boot add-on that makes each REST endpoint's function orchestration explicit. An endpoint's steps, conditional branches and error flows are declared in a single YAML file, and the file's directory path mirrors the URL (officefloor/rest/greeting/{name}.GET.yml maps to GET /greeting/{name}).

Why it qualifies? Criterion (c), a unique approach: OfficeFloor is built on a distinct paradigm, Inversion of Coupling Control, which separates three concerns most frameworks conflate: Continuation Injection (orchestrating functions), Thread Injection (assigning threads to functions), and Dependency Injection (injecting state). The approach is documented in a peer-reviewed paper and an introductory article:

What distinguishes it from other entries in the section: the other REST Frameworks listed handle routing and binding through annotations or code, where an endpoint's flow is implicit in the call stack. OfficeFloor's differentiator is that the orchestration is explicit and external. One readable YAML file per endpoint, with the directory layout acting as a direct index from URL to the code involved. I'm not aware of another entry in the section that takes this approach.

Why the pattern is timely: this explicit structure has also become more practically relevant with AI-assisted development. Because routes are enumerable by listing a directory and each endpoint's flow and classes are named in one file, tools can navigate from a URL straight to the relevant code without parsing scattered annotations. I mention this only as context; the novelty above stands on its own.

Compliance:

  • Added in ascending alphabetical order (between Microserver and Rapidoid).
  • Format NAME - DESCRIPTION., single sentence, ends with a period.
  • Single pull request for this one suggestion.
  • Open source under the Apache License 2.0; documentation in English.

Summary by cubic

Add OfficeFloor to the REST Frameworks list in README. It’s a Spring Boot add-on that makes each endpoint’s flow explicit in one YAML file whose directory path maps to the URL.

Written for commit 6b01ff4. Summary will update on new commits.

Review in cubic

@sagenschneider sagenschneider changed the title OfficeFloor Add OfficeFloor to REST Frameworks Jul 5, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant