IBM Acquires UStream, Forms New Cloud Video Unit
techcrunch.com
techcrunch.com
In 2011 the company rebooted itself to a B2B direction - see http://www.businessinsider.com/this-once-red-hot-startup-had.... This direction has only been a modest success. For a bootstrapped company it would have been completely fine to go on like that indefinitely, but for a VC investment heavy one, this - or any other - sale must have been in the making since the hopes of an IPO have clearly disappeared.
One thing the article doesn't mention is that this aquisition makes a lot of sense for IBM. They get access to a lot of businesses who host their internal video streaming on UStream, like Facebook (company update videos all running on it). Also the main UStream engineering office is in Budapest, Hungary, where there is a large IBM office as well, so that will make integration smoother.
UStream employees who joined to disrupt the startup consumer video space a couple years back - welcome to IBM. I hope you've gotten some handsome payouts or golden handcuffs - and congratulations.
MSFT? 73B in 2012 to 93B in 2015. Solid growth.
IBM: from 103B in 2012 down to 82B in 2015.
So yeah, Apple and MS are growing, while IBM is declining.
What do you think they should be doing that's modern, cool and not 5-10 years behind?
Unikernels? X-for-Y services ( Uber for dogs )?
Basically, IBM is still fundamentally a consulting "solutions" company; their products are things they needed to build to solve a particular recurring consulting problem for their clients, that couldn't be solved with an application of off-the-shelf technology from a partner. This is reflected in IBM's own culture; we'll also look for an off-the-shelf solution[0]—or ask a partner to tailor their product to us—before even considering building something internal. "Scratching an itch" infrastructure projects like Facebook's Cassandra just don't really happen here.
I doubt IBM could have "productized the infrastructure" the way Amazon did to end up with AWS; IBM doesn't have any unique infrastructure. BlueMix, such as it is, isn't a reflection of anything we were already doing; it was simply a de novo solution to a particular recurring consulting problem with unique constraints (high levels of isolation and on-premise collocation) that meant we couldn't just sell the client a solution by some IaaS partner of ours. For internal projects, we frequently still just use AWS or DigitalOcean or whathaveyou (although this is changing as BlueMix becomes more competent to serve our own particular needs as an "internal customer.")
---
[0] ...as long as it's not built by one of our competitors in the "all things to all people megacorp" world. We use Slack, but turning on Google Docs integration is against security policy: we trust a small company like Slack with our IP, but trusting Google is right out.