Yoshi Server

Zero boilerplate, convention-over-cofiguration web server

Problems today

• Boilerplate/setup code:
  • Longer learning curve
  • Developers move slower in a bigger codebase
  • Optimally, our app should only include application logic
• The developer experience can be better:
  • Clear errors and type checks/completions

Our goals

• Reduce the amount of boilerplate required to write a server.
• Abstract the communication between the client and its server.
• Improve the developer experience with type checks and clear error messages.

We have a proposal

• Proposed APIs are new
• May have a few bugs
• We need your feedback

Demo :)

Recap

• We should focus on application logic.
• Route functions: external routes.
• Server functions: internal APIs.
• Consuming server functions with yoshi-server-client.
• React bindings with yoshi-server-react.

Questions?

• We need your feedback in an open RFC: https://github.com/wix/yoshi/pull/1476
• We need your feedback and you can try it out in a version soon.