A 2019 Forrester study sponsored by GitLab quantified found that more than three-quarters of organizations use at least two software delivery toolchains, with the average organization having six or more tools per toolchain. Based on a survey of 252 IT professionals with responsibility over toolchain management, the study also reported that ensuring security (45%) and visibility into maintenance (39%) are the top process challenges teams face with their toolchain.
And this is where DevOps tool vendors now see opportunity. The mounting tax of maintaining tools has grown so extensive that offering an all-in-one solution may just be the trick to get development teams unstuck and the innovation train rolling even faster.
Nice talk from James Lewis on doing a microservices approach to solving a banking system problem.
In the context of our devops coverage, we often speak about the ongoing need for new application development (appdev) approaches caused by emerging drivers such as mobile, social and cloud platforms. Cloud-native apps beg for different architectures than the classic, on-premises three-tiered approach, while the need to integrate with more services than ever has been charging along since the days of mashups-cum-composite applications. In short, companies are always seeking new ways to write and deploy apps, especially in the enterprise space, where complete greenfield opportunities are not as plentiful as they are in the consumer segment. Enterprise systems often have numerous legacy data stores and business processes that must be integrated, all with enterprise-grade governance, risk, and compliance (GRC).
As we noted when we initiated coverage of EnterpriseWeb last year, the company has an ambitious proposal to address many of these concerns with its ‘everything platform.’ Marketing an all-inclusive platform like this can be difficult, especially with so many contenders in the space. However, the company reported bookings of about $2m for 2012 and says it is now closing deals of $500,000-2m.
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.
One of the first pieces I’ve written at the new analyst shop is now free, thrust out beyond the 451 paywall. I’m rebooting the application development coverage at 451 that’s been dormant for around 5 years. Don’t read that wrong, various aspects have been covering it here and there, but there hasn’t been an analyst focused on it. As such, I wanted to layout my “state of the union” of development.
Not too long ago, when Web applications dominated the software-development world, a developer’s primary decision was choosing a framework from the multitude of Web frameworks fine-tuned in the 2000s. Three forces have been changing that status quo in recent years: new devices and client delivery mediums, fragmentation of frameworks and platforms, and a renewed focus on design driven by catering to end users – not just IT buyers.
If I wanted to really summarize it, I’d say it was fragmented: more frameworks, delivery options, and end-clients than were available when I was a young programmer. It used to be just .Net and Java, desktop and web. Now there’s all sorts of languages, all sorts of ways to deliver software (through public cloud, traditional, as heavy GUIs, etc.), and all sorts of “screens” (as Adobe used to put it).
In addition to describing these “three forces,” I also wanted to point to how they might effect various folks in the tech ecosystem, like ISVs, service/cloud providers, and regular old companies inching into the whole “software is eating the world” jag.
Anyhow, tell me what you think. I’m hoping to evolve these ideas and explain-out the little nooks and crannies ongoing.