http-decision-diagram VS webmachine

Compare http-decision-diagram vs webmachine and see what are their differences.

http-decision-diagram

An activity diagram to describe the resolution of HTTP response status codes, given various headers. (by for-GET)

webmachine

A REST-based system for building web applications. (by webmachine)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
http-decision-diagram webmachine
3 2
3,541 1,498
0.1% -0.1%
1.9 2.9
about 1 year ago 2 months ago
JavaScript Erlang
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

http-decision-diagram

Posts with mentions or reviews of http-decision-diagram. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-28.

webmachine

Posts with mentions or reviews of webmachine. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-08.
  • Work in progress on a port of Webmachine
    4 projects | /r/Common_Lisp | 8 May 2023
  • Best Practices for REST API Design
    7 projects | news.ycombinator.com | 22 Feb 2021
    I interrupted my reading at 'Accept and respond with JSON' to write this comment, before I skipped over that section and returned to reading the rest.

    Folks that aren't aware of Webmachine should take a look:

    https://github.com/webmachine/webmachine

    The 'Accept' header should determine the response type, but content negotiation is something that few bother to implement. Webmachine does that for you.

    Also, shameless plug for my OCaml port:

    https://github.com/inhabitedtype/ocaml-webmachine

What are some alternatives?

When comparing http-decision-diagram and webmachine you can also consider the following projects:

api-guidelines - Microsoft REST API Guidelines

google.aip.dev - API Improvement Proposals. https://aip.dev/

OpenAPI-Specification - The OpenAPI Specification Repository

swagger-tools - A Node.js and browser module that provides tooling around Swagger.

grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec

cl-webmachine - HTTP Semantic Awareness on top of Hunchentoot

snooze - Common Lisp RESTful web development