Feeds

Beware Abe Lincoln-looking code pros trying to sell you on LOBDOPs

All beard, no 'tache types... we're all sausage-makers now

Internet Security Threat Report 2014

Time spent at the QCon software developer conference and exhibition in London this week comes with certain guarantees.

There will always be free T-shirts on every stand, gummy bears or jellybeans if you’re lucky, and a high footfall put down by the serious coding cognoscenti.

And mixing among the Abe Lincoln “beard but no moustache”-styled code pros here are the obligatory tech-company evangelists, salesmen without a commission. What was their beef this year? Was it more sound bites like “data is the new currency” and such like?

Talk this year in several circles centered on DevOps, something called “social coding” and collaboration, the tried-and-tested idea of peer review and continuous delivery, on smart file depository usage and, of course, big data analytics.

The difference is that there is an open willingness to discuss how much of these processes, methodologies and approaches we will see executed at a deeper level.

Vendors and their evangelists are always trying to convince us their tools will “reduce complexity” (yawn) and help make "coding and application builds possible for everyone".

"Everyone?" Isn’t that like putting the power of a Ferrari in the hands of a learner driver? Won’t this see business types crash the app dev project?

If we accept that Facebook updates 25 times a day (or whatever it is) and that web and mobile front ends are subject to rapid change, do these rapid workflow models translate well enough to handle work carried out behind the firewall, deep in the datacentre and across the mainframe?

You want the data? You can't HANDLE the data

European director for Perforce Mark Warren says that peer code review is extending its scope beyond its traditional developer domain and now also welcoming in business, legal, compliance and risk specialists.

“The effect of this is that although it had previously been assumed continuous delivery would not be as prevalent behind the firewall or at the mainframe level (where you might expect updates only annually or monthly), we are seeing more rapid cycles starting to impact the way back end enterprise assets are constructed,” said Warren.

Elasticsearch is singing a similar tune. The open-source search and analytics engine company reckons it can help "empower DevOps" (but doesn’t everyone right now?) with its "logstash" central repository for all log data.

So logstash gathers log data in the form of tweets, syslogs, Apache web log files etc (basically anything with a time stamp) and Elasticsearch is capable of running a fine grain query across that data. The analytics resulting from this comparatively low-level data can then be fed into visualisation tools such as graphs and Excel sheets, or to the command line.

Surely that’s like giving airplane passengers a full list of avionics checkpoints and an ongoing data feed from air traffic control on every New York to London return?

None of the vendors were as open about discussing the implications and ramifications opening up access this deeper system information.

“GitHub has used Elasticsearch’s analytics to track and analyse code exceptions generated by the various software components that power GitHub itself,” said Elasticsearch community manager Leslie Hawthorn. “It’s all basically about analytics insight that goes on behind the firewall.”

Only Azul Systems chief technology officer Gil Tene warns we shouldn’t get carried away with ourselves. The speed at which continuous delivery updates and rapid analytics of this kind work is predominantly found within enterprise applications – ones you can interact with through a web-facing front-end, he says.

“We ship a Java Virtual Machine. We can’t just press a button and switch versions when we want to give our customers something new,” said Tene. “Plus, anyway, customers don’t want 75 releases a year: they want four.”

Is there a key trend and, ahem, "takeaway" here? Will access to this system information mean that we see DevOps rebranded as System DevOps or something ghastly? It is more likely to become some more bastardised Line Of Business DevOps version of itself - and that will be LOBDOPS.

The message? Get ready for vendors trying to sell you on LOBDOPs. ®

Security for virtualized datacentres

More from The Register

next story
Microsoft WINDOWS 10: Seven ATE Nine. Or Eight did really
Windows NEIN skipped, tech preview due out on Wednesday
Business is back, baby! Hasta la VISTA, Win 8... Oh, yeah, Windows 9
Forget touchscreen millennials, Microsoft goes for mouse crowd
Apple: SO sorry for the iOS 8.0.1 UPDATE BUNGLE HORROR
Apple kills 'upgrade'. Hey, Microsoft. You sure you want to be like these guys?
ARM gives Internet of Things a piece of its mind – the Cortex-M7
32-bit core packs some DSP for VIP IoT CPU LOL
Microsoft on the Threshold of a new name for Windows next week
Rebranded OS reportedly set to be flung open by Redmond
Lotus Notes inventor Ozzie invents app to talk to people on your phone
Imagine that. Startup floats with voice collab app for Win iPhone
'Google is NOT the gatekeeper to the web, as some claim'
Plus: 'Pretty sure iOS 8.0.2 will just turn the iPhone into a fax machine'
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.