hhow09 / gophercises Goto Github PK

review the flush timing

There are some important considerations while implementing Log. It's important to make sure that entries written to the log file are actually persisted on the physical media. File handling libraries provided in all programming languages provide a mechanism to force the operating system to 'flush' the file changes to physical media. There is a trade off to be considered while using flushing mechanism.

Flushing every log write to the disk gives a strong durability guarantee (which is the main purpose of having logs in the first place), but this severely limits performance and can quickly become a bottleneck. If flushing is delayed or done asynchronously, it improves performance but there is a risk of losing entries from the log if the server crashes before entries are flushed. Most implementations use techniques like Batching, to limit the impact of the flush operation.

Ref

• cassandra commitlog

• https://build-your-own.org/database/
• eatonphil/gosql
• krasun/gosqldb

https://github.com/julienschmidt/httprouter

How does it work?

The router relies on a tree structure which makes heavy use of common prefixes, it is basically a compact prefix tree (or just Radix tree).

Priority   Path             Handle
9          \                *<1>
3          ├s               nil
2          |├earch\         *<2>
1          |└upport\        *<3>
2          ├blog\           *<4>
1          |    └:post      nil
1          |         └\     *<5>
2          ├about-us\       *<6>
1          |        └team\  *<7>
1          └contact\        *<8>

https://github.com/etcd-io/etcd

• example-golang
  • Golang, Gin Framework, GQLGen GraphQL, Resful, Authentitacion with JWT and much more.

https://github.com/hibiken/asynq

do some example exercise

check this
https://github.com/bwmarrin/snowflake

tinyrpc

balancer

miniredis