Welcome!

Java IoT Authors: Liz McMillan, Elizabeth White, Yeshim Deniz, Tim Hinds, Douglas Lyon

Related Topics: @DevOpsSummit, Java IoT, Linux Containers, @CloudExpo

@DevOpsSummit: Blog Post

To Ensure Continuous Delivery By @TrevParsons | @DevOpsSummit [#DevOps]

Although continuous integration and continuous delivery are sometimes used synonymously, they are actually separate activities

Four Ways to Ensure Continuous Delivery Helps, Not Hurts

Customer demands aren't the only thing pushing development and operations teams into more frequent software releases. It is also need for quicker feedback on product quality, the desire to reduce bottlenecks in operations teams, and the goal to utilize less overhead on projects.

The concepts and spirit of continuous delivery are well known. However, organizations with existing applications starting to implement continuous delivery still have a lot to consider.

Making sure continuous delivery helps, not hurts your organization, is key to long-term success.

Faster features, quicker feedback, less snags, and more efficient teams are all good drivers to adopting continuous delivery (CD) and integration (CI).

Unless your organization was born with continuous delivery, making the move can be tricky. You have a few choices:

  1. Slip stream CI or CD into the current delivery pipeline. Sometimes, introducing CI into your development processes is not too much of a challenge, with the hardest part being the construction of a flexible integration lab. Because you can keep your existing waterfall release process, it looks and feels a lot like a more flexible UAT environment. CD is different however; inserting CD into existing processes can be complicated. It's obviously much different, and can create timing issues with roadmaps and previous releases.
  2. Start with a parallel development and operations group that is built bottom up for continuous delivery. Usually this requires a compelling event, like a new major version of an application, or an on-premise client application that is moving to a web application for it to make sense. The cost of another group is high, but it is an ideal opportunity to leverage all DevOps has to offer.
  3. Re-building the existing development process from scratch. While this is the best way to keep team structure intact (compared to option two), it requires you to allocate significant time when you're not releasing, and has a high failure rate.

What's the difference between CI and CD?
Although continuous integration and continuous delivery are sometimes used synonymously, they are actually separate activities with nearly identical tooling and processes. CI can be leveraged by almost any organization, even those stuck in waterfall-based projects, simply because the risk is much lower. However, CD impacts all users, and production infrastructure.

Now lets explore continuous delivery more.

In the spirit of DevOps the first and second option above make the most sense.

Option one allows you to start learning and leveraging the results driven culture without having a large impact on current production releases. This allows the team to learn about the processes and speed at which things happen, while maintaining the comfort level they're used to. The downside is it might encourage teams to stick with old habits, and eventually if not pushed forward, encourage reverting back to old ways.

Option two is ideal if there is a compelling event, staff, and budget to support it. This option allows you to leverage all DevOps tools right away, without much concern about integrating with existing components. The goal being that eventually everyone will move to the new processes after the support for the older waterfall driven applications die off.

Several very large software companies have successfully leveraged this approach. Now, large (previously non-technical) organizations with a combination of line-of-business applications and mobile and web applications benefit from this approach tremendously.

Both of these options have their pros and (more importantly) their cons. Startups designed from scratch with continuous delivery may not have addressed them, but you can.

There are four elements of CD that can pose serious challenges down the road.

  1. Ability to revert
  2. Tying Infrastructure and Application Layers
  3. Bugs, bugs, and more bugs
  4. Blind spots

1. Ability to revert
"Delivery" is the most important part of the modern release pipeline. It's emphasis is on getting code to market faster and being results driven.

Inevitably things will break (if they don't your team is not moving at the appropriate pace). Because things will break, reverting releases to previous versions is a very important component of the process. But reverts are not allows code; they can be configurations and even machines.

Building in great reverting mechanisms, which are fully tested against a series of previous releases, help teams know that their revert engine is there when they need it. It is wishful thinking to believe that release automation tools will do this for you; they won't. You need to perform regression testing on your revert process, at least early on, because teams will often forget dependencies at first run.

Having the analytics to let teams know what configurations look like before, and after a release, is critical to stay aware of all the changes that are happening between versions; both in the application and infrastructure.

2. Tying Infrastructure and Application Layers
With the speed of releases and the speed at which frameworks, web servers, and backbends that applications utilize are updating, it is critical that software releases be tied to their associated infrastructure.

A revert will get you back to a previously known good state, but it won't fix the problem. Every organization will have a different way of doing this, but without the correlation, development and operations will play ping-pong with issues and their potential resolutions.

It's a classic problem to have things such as new frameworks and patches run in integration environments but not production. This is a catalyst for wide spread issues. Without knowing the relationship of a release to infrastructure, a huge amount of time can be wasted trying to spot these issues and quickly starts looking like waterfall again.

3. Bugs, bugs, and more bugs
Let's say a small bug makes it through one release, two releases, or maybe even three. This means code on top of bad code has been released. Unfortunately this happens a lot, however with the power of frequent releases and active feedback it will eventually get caught.

Catching the bug is not the problem.

The problem is understanding exactly where the bug is. Sometimes a new feature using buggy functionality might be operating exactly as intended, but what it was written on top is not. This is why having a strong system for performance testing, QA, and QE is as critical to continuous delivery as tools like Jenkins, and GO.

4. Blind spots
These bugs often occur because of blind spots in the environment and poor analytics. These are areas in the infrastructure and code that teams can't always get a clear picture of. The issues end up surfacing in support tickets, complaining users, or potentially outages.

Blind spots should be avoided at all costs.

You achieve this by building in a culture of analytics first, and analytics everything, very early on. Making sure that operations and development teams know to produce analytics for all systems and applications, and where to push them. Leverage integrations of tools like Logentries with APM tools like New Relic to help gain the insights you need.

CI/CD give teams more flexibility and the ability to create better products. For teams with existing applications, it is also a fantastic opportunity to move in a new direction that keeps you competitive. The shift may not always be easy, but the rewards are well worth it. Taking into consideration the above aspects of CD that could potentially pose challenges down the road will help these teams implement CD without harm. Let us know what you think in the comments below.

More Stories By Trevor Parsons

Trevor Parsons is Chief Scientist and Co-founder of Logentries. Trevor has over 10 years experience in enterprise software and, in particular, has specialized in developing enterprise monitoring and performance tools for distributed systems. He is also a research fellow at the Performance Engineering Lab Research Group and was formerly a Scientist at the IBM Center for Advanced Studies. Trevor holds a PhD from University College Dublin, Ireland.

@ThingsExpo Stories
BnkToTheFuture.com is the largest online investment platform for investing in FinTech, Bitcoin and Blockchain companies. We believe the future of finance looks very different from the past and we aim to invest and provide trading opportunities for qualifying investors that want to build a portfolio in the sector in compliance with international financial regulations.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, whic...
Imagine if you will, a retail floor so densely packed with sensors that they can pick up the movements of insects scurrying across a store aisle. Or a component of a piece of factory equipment so well-instrumented that its digital twin provides resolution down to the micrometer.
In his keynote at 18th Cloud Expo, Andrew Keys, Co-Founder of ConsenSys Enterprise, provided an overview of the evolution of the Internet and the Database and the future of their combination – the Blockchain. Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settle...
Product connectivity goes hand and hand these days with increased use of personal data. New IoT devices are becoming more personalized than ever before. In his session at 22nd Cloud Expo | DXWorld Expo, Nicolas Fierro, CEO of MIMIR Blockchain Solutions, will discuss how in order to protect your data and privacy, IoT applications need to embrace Blockchain technology for a new level of product security never before seen - or needed.
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, discussed some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he covered some of the best practices for structured team migration an...
No hype cycles or predictions of a gazillion things here. IoT is here. You get it. You know your business and have great ideas for a business transformation strategy. What comes next? Time to make it happen. In his session at @ThingsExpo, Jay Mason, an Associate Partner of Analytics, IoT & Cybersecurity at M&S Consulting, presented a step-by-step plan to develop your technology implementation strategy. He also discussed the evaluation of communication standards and IoT messaging protocols, data...
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even coding. Raju Shreewastava is the founder of Big Data Trunk (www.BigDataTrunk.com), a Big Data Training and consulting firm with offices in the United States. He previously led the data warehouse/business intelligence and B...
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
When shopping for a new data processing platform for IoT solutions, many development teams want to be able to test-drive options before making a choice. Yet when evaluating an IoT solution, it’s simply not feasible to do so at scale with physical devices. Building a sensor simulator is the next best choice; however, generating a realistic simulation at very high TPS with ease of configurability is a formidable challenge. When dealing with multiple application or transport protocols, you would be...
Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...
We are given a desktop platform with Java 8 or Java 9 installed and seek to find a way to deploy high-performance Java applications that use Java 3D and/or Jogl without having to run an installer. We are subject to the constraint that the applications be signed and deployed so that they can be run in a trusted environment (i.e., outside of the sandbox). Further, we seek to do this in a way that does not depend on bundling a JRE with our applications, as this makes downloads and installations rat...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
In this strange new world where more and more power is drawn from business technology, companies are effectively straddling two paths on the road to innovation and transformation into digital enterprises. The first path is the heritage trail – with “legacy” technology forming the background. Here, extant technologies are transformed by core IT teams to provide more API-driven approaches. Legacy systems can restrict companies that are transitioning into digital enterprises. To truly become a lead...
Digital Transformation (DX) is not a "one-size-fits all" strategy. Each organization needs to develop its own unique, long-term DX plan. It must do so by realizing that we now live in a data-driven age, and that technologies such as Cloud Computing, Big Data, the IoT, Cognitive Computing, and Blockchain are only tools. In her general session at 21st Cloud Expo, Rebecca Wanta explained how the strategy must focus on DX and include a commitment from top management to create great IT jobs, monitor ...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
The IoT Will Grow: In what might be the most obvious prediction of the decade, the IoT will continue to expand next year, with more and more devices coming online every single day. What isn’t so obvious about this prediction: where that growth will occur. The retail, healthcare, and industrial/supply chain industries will likely see the greatest growth. Forrester Research has predicted the IoT will become “the backbone” of customer value as it continues to grow. It is no surprise that retail is ...