You probably still want to know who actually built a given container and what’s running in it.
“The site reports it hosts 25 million source code repositories, and has 10 million registered users and 33 million unique monthly visits.” No word in the article in revenue or enterprise sales.
I’ve been speaking with StackStorm on and off for a few months now. I finally got around to writing up a report on them, available for clients.
Here’s the 451 Take:
StackStorm fancies itself an automation company, and with experience from Opalis Software, it’s little wonder. What’s interesting about its approach is that it’s automating the DevOps pipeline, including the continuous integration/continuous delivery (CI/CD) process. This may seem like a minor concern, namely, working on developer tools. And ‘developers don’t pay for anything,’ right? However, in cloud native application and DevOps teams, the CI/CD pipeline is the core factory for a company: it’s a mission-critical process that needs as much monitoring and automation as production itself. If your business depends on being able to deploy new code every week – or daily – anything that slows down that pipeline is bad, very bad. Not only that, integrating the pipeline with production monitoring and automation helps realize the full continuous delivery vision. Hence, StackStorm finds itself in an interesting position, vision-wise: we’ll take care of the new mission-critical asset for you, the DevOps pipeline. Few other vendors have that scope of vision, at the moment at least.
I had a briefing with Serena a short while ago around the new release of their ALM product Dimensions. They’re interesting to talk with because of their conservative customer base: so it’s a good way to track mainstream adoption of emerging developer practices. Things seem to be moving along nicely there. Since changing PE hands, they seem to have a renewed interest in shipping new releases, which should be fun to watch as well.
451 clients can read the full report, but here’s the 451 Take:
While our research in devops shows strong interest in the market, with developers in the technology sector ‘getting it,’ mainstream adoption of devops (or even continuous delivery) practices is still lagging. Serena has long serviced a chunk of this ‘mainstream’ pool in the form of the more conservative developers in finance, insurance, defense and other highly regulated industries. These teams require maximal governance, risk and compliance trappings; often need to integrate with a variety of not-so-new tools and processes; and are looking for very safe bets when it comes to tool suites. Thus, a company like Serena, with more than 450 customers, is responsible for bringing new innovations in application life-cycle management (ALM) to these customers, and is seeking to do just that with the Dimensions 14 release. The reception should be good, if slow, since the technologies and practices in software development have been experiencing a pleasant refresh in recent years. Serena will have to contend with several competitors – like Atlassian and TaskTop, which are similarly bringing fresh takes on ALM to the market and increasingly looking to sell into conservative accounts.
If you’re not a client, you can always sign up for for a free trial.
Version 3.5 of TaskTop is a dot release with some fun stuff scurrying around in the background.
Here’s the 451 Take:
Tasktop has done well in recent years as a pragmatic way to connect together disparate silos in the application lifecycle development space. The approach Tasktop is taking to better unify the process of getting software out the door is unique and encouraging, as its wide array of OEM partners attests. These partners should, ostensibly, be doing what Tasktop does on their own, but instead they partner with the small company. Tasktop’s mission is simple in concept, but complex in implementation: instead of requiring different teams in large companies to use the same tool to keep the ALM data and process properly synchronized across silos, Tasktop Sync acts as sort of ALM-integration and extract, transform and load (ETL) middleware to keep all the silos up to date. This current release is emblematic of that task in that it adds support for additional tools and rolls out some of the initial end-to-end reporting done over all the different tools and teams.
Devops hasn’t progressed far enough to need something like Tasktop, but as we noted in our coverage of Sync 3.0, it’s starting to smell more and more like DevOps when Tasktop comes into the room. Perhaps it’ll help hammer out the idea of ‘BizDevOps’ along with other vendors that are looking to more tightly couple business stakeholders and process to the nascent devops tool chain.
Atlassian released an ALM bundled centered around git recently. I wrote up a report on that release, git in broader terms, and of course profiling the current state of Atlassian.
Here’s the 451 take:
Git Essentials is a natural bundling move by Atlassian. The company has long been expert at tracking mainstream needs for software development teams and acted as a sort of safety bumper around the leading edge of developer practices and technologies: taking and creating early adopter technologies and making them enterprise ready. Competition in the ‘enterprise git’ market is just beginning, and this is a wise time to enter with a larger offering than the stand-alone Stash and Bitbucket git version control product and service. Atlassian’s popularity and growth (with $149m in FY 2013 revenue) is evidence of both the company’s momentum and the growing interest in the application development space.
[T]here will be classes of developers that go after Git and they’ll love Git for what it allows them to do which is to stay off the radar until their tiered promotion gets it ultimately to visibility, but there will be other shops that want to have that visibility the entire time and their compliance or governance or whatever the management driven stuff that is required will keep it around.