There are rumors that Summize has been acquired by Twitter. It has people chattering.
Some worry that the acquisition will hurt the effort to make Twitter scale. It can’t and won’t.
I believe Twitter’s engineering team is headed up a mountain (they need to switch architectures at a low level), but that they finally know which mountain. True, it’s a tall mountain not quickly climbed. But they finally know their problems and have people in place. Better days ahead.
Others worry that Twitter’s scaling ills will infect Summize. I don’t think that’s possible because they are distinctly different engineering problems. Summize is “fresh search,” an understood and known problem that Summize apparently designed for from the beginning. Twitter, in contrast, evolved a product into a service that no longer matches their architectural model. It didn’t start out as (and therefore wasn’t built to be) a massive-to-massive (when each massively is unique, personal, exponentially expanding) real-time messaging protocol. I believe architectures exist for that problem space, but unfortunately that’s not how Twitter was initially built.
Put briefly, Twitter’s already on the path to health and Summize is immune from Twitter’s disease, so it should all work out fine.
While they are different systems, they may be complimentary. Jettisoning Twitter’s track and reply functionality to Summize’s infrastructure may offer Twitter engineers the headroom they need to roll updates into Twitter’s codebase with a bit of a cushion.