twin / g8

⛩️ Go library for protecting your HTTP handlers

Hey, I'm TwiN! 👋

Just another person trying to embrace their passion prevent the vicissitudes of life from taking away their passion.

Currently building my first SaaS during my free time: gatus.io

📝 Latest Blog Articles

• Securing Gatus with OIDC using Auth0
• Mocking HTTP requests in Go
• Bit Fields: Squishing Booleans Using Bitwise Operations
• Writing Good Documentation
• Shit Programmers Say: “Just Scale Up”
• Performance, Benchmarking and Allocations in Go
• What Programming Means to Me
• Go Concurrency: GoRoutines, Worker Pools and Throttling Made Simple

📊 Statistics

g8's Issues

Implement caching in the ClientProvider

Implementing a cache with a configurable TTL as well as a configurable maximum size in ClientProvider could be very useful to help preventing unnecessary load on whatever service or infrastructure component ClientProvider's getClientByTokenFunc function is calling.

The implementation:

• Must be able to have a maximum cache size (e.g. 10000)
• Must be able to have a configurable TTL (e.g. 1 hour)
• Must be able to cache invalid tokens with a shorter entry TTL (e.g. 30 minutes)

Being the self-promoting person that I am, I think TwinProduction/gocache would fit this role perfectly.

Add support for rate limiting

It would be nice to have a configuration for rate limiting on Gate.

Something like this:

gate := g8.NewGate(nil).WithRateLimit(100)

where 100 is the maximum number of requests per second.

Add a way to rate limit based on a header value

Support using cookie as a form of identification

Rather than only supporting the Authorization header as a way to identify a user, it would be nice if we could use the client provider to retrieve the user through a session cookie.

feat: ClientProvider.cache as an interface to support external cache (e.g. redis)

Describe the feature request

At present it looks like the client provider cache field is tightly coupled to the gocache.
If a user wants to also use an external/shared/distributed cache then this isn't possible.
It would be nice to allow more flexibility to the user in which caching solution they wish to use.

Why do you personally want this feature to be implemented?

to allow flexibility in choice of cache solution.

How long have you been using this project?

No response

Additional information

No response