Articles

Software developers have spent the last decade talking about Continuous Delivery and the benefits of delivering working code as often as possible. But it turns out that’s only one part of the whole picture of software delivery. Modern teams actually have three distinct outcomes they are trying to achieve — a holy trinity of continuous, incremental, and progressive delivery. Each of these delivery practices can help your team move faster with less risk.

Continuous Delivery

Continuous Delivery is a set of practices that ensure your code is always in a deployable state. You accomplish this by increasing the frequency at which code is committed, built, tested, and deployed-steps that in the past only occurred at the end of a project when it was ‘code complete’.

Source de l’article sur DZONE


“DevOps is Agile on steroids — because Agile isn’t Agile enough.”

So says Jim Bird, the CTO for BiDS Trading, a trading platform for institutional investors. Jim continued, "DevOps teams can move really fast…maybe too fast? This is a significant challenge for operations and security. How do you identify and contain risks when decisions are being made quickly and often by self-managing delivery teams? CABs, annual pen tests, and periodic vulnerability assessment are quickly made irrelevant. How can you prove compliance when developers are pushing their own changes to production?"

Jim was presenting at the 2018 Nexus User Conference on Continuous Delivery. Pulling on his 20+ years of experience in development, operations, and security in highly regulated environments, Jim laid how and why Continuous Delivery reduces risk and how you can get some easy wins toward making it more secure.

Source de l’article sur DZONE

Continuous Delivery is no longer a value-enhancing strategy, it is a much-needed approach in software development and release lifecycle. It has substantially changed the way enterprises test and launch their applications in a volatile consumer ecosystem. The demand for Intelligent Applications is on the rise. In fact, it is predicted that almost all the applications will be delivered with embedded intelligence. It practically implies that these applications will have the capability to scrutinize historical and real-time data to deliver customized experiences and results to the end-users by leveraging Machine Learning technologies. Hence, testing these applications will need a relevant Test Automation strategy and a Continuous Delivery plan.

In the current Digital ecosystem, consumers are swarmed by chatbots and virtual assistants across diverse websites and applications. These features are not only automating basic activities, but are also delivering enhanced and personalized experiences. At a recent Google conference, CEO Sundar Pichai opened the event by stating, "We’re moving from a mobile-first to an AI-first world." Hence, due to growing business mandate and evolving consumer preferences, the need to build such robust applications is increasing by the day.


Source de l’article sur DZONE (AI)

The following is an excerpt from a presentation by Ron Forrester and Scott Boecker from Nike, titled “DevOps at Nike: There is No Finish Line.

nike-does-us-2017You can watch the video of the presentation, which was originally delivered at the 2017 DevOps Enterprise Summit in San Francisco.

Source de l’article sur DZONE