mirror of
https://github.com/Expand-sys/CCash
synced 2025-12-17 00:22:14 +11:00
Update implementation.md
This commit is contained in:
parent
5eaf38baab
commit
ef69b29761
1 changed files with 3 additions and 1 deletions
|
|
@ -24,6 +24,8 @@ base64 decoding is required for Basic Auth so I used this clean and fast solutio
|
||||||
simdjson was the fastest JSON parsing I could find, its used for request parsing.
|
simdjson was the fastest JSON parsing I could find, its used for request parsing.
|
||||||
## [Drogon webframework](https://github.com/an-tao/drogon)
|
## [Drogon webframework](https://github.com/an-tao/drogon)
|
||||||
at the time of making this doc Drogon is the 3rd fastest web framework as per [this](https://www.techempower.com/benchmarks/#section=data-r20&hw=ph&test=composite) sites metric of measuring web frameworks, it also has multi threading support.
|
at the time of making this doc Drogon is the 3rd fastest web framework as per [this](https://www.techempower.com/benchmarks/#section=data-r20&hw=ph&test=composite) sites metric of measuring web frameworks, it also has multi threading support.
|
||||||
|
|
||||||
|

|
||||||
## Sparse saving
|
## Sparse saving
|
||||||
#### Saving on close
|
#### Saving on close
|
||||||
when the program is interupted with CONTROL + C it will save before closing the webserver, **it will not however save during a crash**.
|
when the program is interupted with CONTROL + C it will save before closing the webserver, **it will not however save during a crash**.
|
||||||
|
|
@ -44,4 +46,4 @@ saving is done using FBE, this slightly reduces file size compared to JSON and i
|
||||||
considering phmap and drogon both massively benefit from being multi-threaded it seemed obvious that the entire program should be, this is enabled by default and manually settable at `MULTI_THREADED`. Below are some graphs visualizing the gain of doing so:
|
considering phmap and drogon both massively benefit from being multi-threaded it seemed obvious that the entire program should be, this is enabled by default and manually settable at `MULTI_THREADED`. Below are some graphs visualizing the gain of doing so:
|
||||||
<!-- graph -->
|
<!-- graph -->
|
||||||
## Backwards Compatible API
|
## Backwards Compatible API
|
||||||
versioning is implemented by the endpoints path, for example `/v1`. Breaking changes will ideally be sparse and backwards compatability will be maintained, for example ideally API `v3` instance can still run `v1` endpoints.
|
versioning is implemented by the endpoints path, for example `/v1`. Breaking changes will ideally be sparse and backwards compatability will be maintained, for example ideally API `v3` instance can still run `v1` endpoints.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue