Public RoadMap

[sansyrox]

I've moved away from maintaining a yearly roadmap. We will be following a waterfall style roadmap. We will be focusing on one current major issue and then future issues in the pipeline. Please feel free to use this issue as a place to request features.

Current Area of Focus

• Complete OpenAPI deployment. Blocker feat: override openapi json #961

Future Plans

• Make Robyn faster - eliminate the need for pyo3-asyncio #957
• Support Python 3.13
• Add streaming Responses
• Integrate Pydantic by default
• Middleware Chaining
• Restructure Architecture to fix multiprocessing and dev server
• and more ...

Somethings left from 2023

• implement request validation

  • here I wanted to implement some sort of message validation, and @kliwongan is doing an amazing job here Implement easy access query parameters and request body validation based on query parameters #363

• add support for yields

  • I want to allow yields in the framework. That way we can do some processing after the response has been returned

• complete Strawberry GraphQl support

  • We have an initial integration with Strawberry but we need to create three things
  • Implement class views
  • Implement functional views
  • Add code to the strawberry-graphql repo

• then add a first class support for the database orm (feat: support for structured scaffold in create command #970 )

  • The lack of database support is something that I don't enjoy. I want to add a first class orm support for a database but since Robyn is also a microframework, we would still want to allow the ability swap it out. Like our jinja templates.

• Improve websockets

  • Web sockets are not the fastest right now. Need to improve the speed.
  • allowing blocking options in async web sockets

• Implement SSE

• Default authorization and authentication

  • Add the ability to add default authorization and authentication. But like the templating support, this needs to hot swappable.

• Automatic const request optimization

  • [Feature Request] Add auto request optimization #209

• middlewares:

  • see if the responses are handled the right way in middlewares([Feature Request] Add response body in middlewares before and after request #244)
  • implement chainable middlewares([Feature Request] Add the ability to chain middlewares #206)

Somethings left to do from 2022:

• Make a community of plugins
• Better jsonify method

Feel free to comment with what you think of it and if there are any features that you'd like to have in this roadmap.

[dave42w]

Hi,

1: "Structured Scaffold"

I wonder how the full scaffolding fits long-term with the "community of plugins".

Will it be possible to gradually "migrate" from the "Simple Starter Kit" to the "Structured Scaffold" by adding plugins? My initial reading is that the "Structured Scaffold" has some great features and structure but it goes beyond a structure to include lots of tools that turn Robyn into a very fully featured and opinionated framework. I'd love the option of a structure that provides "separation of concerns and enhanced organization for scaling projects." without immediately pulling in everything including the kitchen sink. It would be great if it allowed me to gradually learn Robyn in a new application without having every tool to also learn from the beginning.

If it were possible I'd like to see all the parts of the "Structured Scaffold" as plugins and clear documentation on how to incrementally upgrade from the Simple Starter Kit.

2. Pydantic and Orm

How will support for both Pydantic and SqlAlchemy work? ("Integrate Pydantic by default" and "then add a first class support for the database orm") My understanding is that at present Sqlalchemy can support DataClass and that you need to use SqlModel if you want to use Pydantic?

3. GraphQl

It doesn't say so but is the "initial integration with Strawberry" fully optional?

4. Default authorization and authentication

"Add the ability to add default authorization and authentication. But like the templating support, this needs to hot swappable." Doesn't this also fit with the plugin community? Make the example https://robyn.tech/documentation/example_app/authentication a plugin and then people can use that as a model for alternative implementations?