Redesign or migration of an existing SSP - toxaaa

toxaaa

- Redesign or migration of an existing SSP
Текст — Over the last year our current SSP has started to feel like a museum piece: old framework, custom patches everywhere, deployment takes ages and nobody really wants to touch core modules. At the same time product keeps asking for new features and better reporting, and devs quietly hint that “on this stack it’ll be painful”. I’m seriously thinking about either migrating to a modern stack or rewriting big chunks from scratch. Has anyone gone through that and survived?

Add To My Bag

Edit Equipment

Reviews/Comments

andreevdarius - 11/20/25
Sometimes watching other teams, you can see two extremes: either they cling to legacy code because “it still works, don’t touch it”, or they jump into a rewrite without a clear plan and then fight fires for months

zazajoj789 - 11/20/25
Personally I went through a similar phase on a previous project where we had to decide what to do with an aging SSP in programmatic. We ended up doing a staged migration instead of a full “big bang” rewrite: split services, gradually move critical pieces to a newer stack, and only then tackle the UI. When we looked for help, we talked to teams like https://geomotiv.com/industries/adtech/ssp/ , who already build and refactor SSP-style platforms, so the conversation was about traffic, QPS and partners, not just about which framework is trendy. It was still a long journey, but at least we didn’t have to turn the lights off while rebuilding everything.

Post A Review

Equipment Ratings

Overall:

Value:

Look:

Performance: