Recently dove into the technical architecture behind RMRK's infrastructure—pretty interesting how they've structured things. Their stack is built on a solid foundation: DigitalOcean and AWS handle the core compute, Cloudflare and Vercel manage edge distribution and deployment. For the data layer, they're running Postgres with Subsquid indexing, serving queries through GraphQL, and using Typesense for search capabilities. The orchestration side leverages Kubernetes with Docker containerization, while Cloudflare Workers handle serverless functions. The frontend is primarily React-based. It's a distributed, scalable approach for handling complex blockchain data and interactions.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
8 Likes
Reward
8
6
Repost
Share
Comment
0/400
AlwaysMissingTops
· 6h ago
NFT infrastructure is really taking off, and using Postgres with Subsquid is indeed stable. But the AWS bill is quite frightening...
View OriginalReply0
FortuneTeller42
· 6h ago
NGL, RMRK's tech stack is indeed quite elaborate, but honestly, it's hard to say how long this setup can last.
View OriginalReply0
MEVHunterBearish
· 6h ago
ngl, this tech stack is quite professional, but why does it have to be so complicated... Cloudflare is only used in two places.
View OriginalReply0
EyeOfTheTokenStorm
· 6h ago
Hmm... The tech stack looks okay, but I'm more concerned about how much TPS and user volume this infrastructure can support. Just stacking AWS + K8s isn't enough.
View OriginalReply0
ApeWithNoChain
· 6h ago
ngl RMRK's tech stack seems a bit over-engineered... Do we really need so many layers?
View OriginalReply0
SurvivorshipBias
· 6h ago
NFT infrastructure is indeed not as simple as it seems. The combination of subsquid with GraphQL is quite sophisticated.
Recently dove into the technical architecture behind RMRK's infrastructure—pretty interesting how they've structured things. Their stack is built on a solid foundation: DigitalOcean and AWS handle the core compute, Cloudflare and Vercel manage edge distribution and deployment. For the data layer, they're running Postgres with Subsquid indexing, serving queries through GraphQL, and using Typesense for search capabilities. The orchestration side leverages Kubernetes with Docker containerization, while Cloudflare Workers handle serverless functions. The frontend is primarily React-based. It's a distributed, scalable approach for handling complex blockchain data and interactions.