Plugin Repository: From a Makeshift Site to an Online Store
summary
A JetBrains talk describes migrating a homemade plugin site into a scalable marketplace by moving plugin files to S3 with CloudFront for global downloads, adding a small Kotlin async Elasticsearch-based service to serve metadata and lists (~2,000 req/min), and introducing a separate .NET backend for ReSharper plugins. Metrics include >1M metadata pulls/day, full lists up to 50 MB, ~70 new plugins/month and ~2 uploads/day, and the marketplace launched with about 100 vendors while metadata load still needs reduction.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:48JetBrains plugin repo
- 3:36Storage solution
- 7:03Current architecture issues
- 11:58Moving to AWS
- 15:37Caching optimization
- 17:43Plugin support .NET
- 20:56Ecosystem services
- 23:02Future tech plans
- 23:48What is a plugin
- 27:54Demo IDE theme
- 31:15Plugin dev contests
- 32:40Paid marketplace launch
- 35:15Collaboration closing
related talks
57mOpening Keynote
01h 13mKeynote
06h 54mJetBrains Plugin Developer Conf 2024
18mFrom Template to Marketplace Creating Your First Plugin
06h 30mJetBrains Plugin Developer Conf 2025
33mThe State of Backstage in 2025
26mBackstage: Shaping the Future Of Developer Experience
24mScaling the Stage: Managing 200+ Plugins & Thousands of Engineers
