It looks like a traffic server is already good enough. We do not need another cache server

[drmingdrmer]

Since there is a powerful opendal as a cache client that deals with object fragmentation and object metadata interpretation.
The server side of the cache becomes a simple key-value-like store.

Thus there is no need to build another service. There is already plenty of software that meets such a need. traffic server is a mature cache server and supports pushing an object to it.

We can just deploy a traffic server cluster as a cache service backend.
Thus this project will be hanging unless any requirements can not be implemented with the traffic server.

@Xuanwo @bohutang @flaneur2020 @lichuang @ariesdevil

[Xuanwo]

• For pushing: https://docs.trafficserver.apache.org/en/latest/admin-guide/storage/index.en.html#pushing-an-object-into-the-cache
• For removing: https://docs.trafficserver.apache.org/en/latest/admin-guide/storage/index.en.html#pushing-an-object-into-the-cache
• For pulling: of course, I can use GET.

Seems enough for now.

[flaneur2020]

is there any equivant service in aws? q.q

[bohutang]

Squid Proxy Cache Server? https://aws.amazon.com/marketplace/pp/prodview-3mzfrlmzpad5i

[wubx]

I understand about cache another thing is that it's a cache for writes. traffic server can't do it.

[drmingdrmer]

I understand about cache another thing is that it's a cache for writes. traffic server can't do it.

It supports active push/remove:

For pushing: https://docs.trafficserver.apache.org/en/latest/admin-
guide/storage/index.en.html#pushing-an-object-into-the-cache
For removing: https://docs.trafficserver.apache.org/en/latest/admin-
guide/storage/index.en.html#pushing-an-object-into-the-cache