orjson VS starlite

orjson is the fastest JSON library available for python. It natively manages dataclass objects, datetime, numpy and UUID objects.

As we began venturing down that road, a few things emerged that would constitute significant changes to some of the core parts of Litestar, but there were two things in particular that started a chain reaction of changes by opening up further possibilities: The new DTOs and our switch from orjson to msgspec.

In version 1.45.0, we introduced msgspec as our serialization backend, replacing orjson. This had some immediate performance benefits, but that's not the main reason we made the switch.

Doesn't orjson do that already?

orjson

For most cases, you would want to go with python’s standard json library which removes dependencies on other libraries. On other hand you could try out ujsonwhich is simple replacement for python’s json library. If you want more speed and also want dataclass, datetime, numpy, and UUID instances and you are ready to deal with more complex code, then you can try your hands on orjson

Try https://github.com/ijl/orjson. Not exactly sure if that can help.

For the past one and a half years 😁. Checkout our docs https://starliteproject.dev/

#1286 is the issue tracking the removal of our last internal Pydantic datastructure, and PR #1382 has the addition of attrs based signature modelling. Once those are merged you will be able to use Starlite without Pydantic.

You can go to Open an Issue and open an issue for a feature request/enhancement and describe basically the behavior you are wanting to see.

Falcon FastAPI Sanic Starlite (disclosure: I do work here)

for server side , starliteproject.dev/, only python async framwork worth looking into.

Well, I'm not objective but I'd say Starlite (https://github.com/starlite-api/starlite) is a might fine codebase. You can also learn a lot about tooling and typing going through it.

I have mentioned your concerns to the Starlite discussions board - https://github.com/starlite-api/starlite/discussions/1183

You can find the complete changelog on our v1.51.0 GitHub release page.