Over a million developers have joined DZone.

The Dawn of Liquid Software

DZone 's Guide to

The Dawn of Liquid Software

Step back from an everyday task and think about how you can automate it. That's one of the ideas of liquid software, explained here by the founder of JFrog.

· DevOps Zone ·
Free Resource

Thanks to Fred Simon, Founder and Chief Architect at JFrog for sharing his thoughts on the future state of DevOps and the concept of liquid software that was introduced at their swampUP! user conference.

What do developers and DevOps teams need to know about Enterprise+?

It's been more than a year in the making based on listening to customers and DevOps users who are thinking about making change quickly. The exponential growth of the JFrog platform and all DevOps tools is pushing users to ask for more and more

Our goal is to put the tools and platform for everyone from code to production without human intervention.

The production environment of customers is getting more geographically disparate, more diverse, more multi-cloud and hybrid. These customers need to have a global picture of what’s going on when they release a new feature or version to know everyone up to date with the same picture.

The goal of JFrog Mission Control is to have an overview of the flow of binaries from development to production verifying all services are running and connected in a secure fashion.

JFrog Xray provides high availability critical assurance to know a package is clean. Two big features of security access, JFrog Access Federation, provides a single distributed view of users and permissions across all geographies and data centers. Geographically dispersed developers have the ability to login to a single platform.

JFrog Distribution enables customers to manage release bundles secured with a signed block of confidence packages and files that will be traced all the way to production. On top of this model we accelerate distribution and traceability to tell which bundle went to which location, along with the capability of re-trying automatically. If there is an announcement about new feature, everyone can see the same thing.

What a use case you would highlight?

The retail industry spends a huge amount of time updating devices with data changes, promotion models, or coupons across all locations, all POS systems, all tablets, and beyond. It requires a huge amount of runtime to update everything. The physics of providing new software could take months. Trials with Enterprise+ reduced months to days. This really impressed our retail clients.  It helps them compete with Amazon. The ability to update software at point-of-sale will be a big differentiator for brick and mortar retailers.

So the future is liquid software?

We want to push the industry to continuous updates. Think about software as evolving since no one wants to suffer the inconvenience and downtime required by running updates.

Today, it's OK to wait for an update but at the end of the day, it’s the laziness of the developers not spending the time, energy, and money necessary to make it easy for the end user.

When it hurts, do it more often. If the whole IT community keeps updating they will make automatically updating software ubiquitous. 

Liquid Software is the future in which developers code high-quality applications securely flowing to end-users with zero downtime. 

What do developers need to keep in mind?

Keep innovating, keep automating, don’t hurt yourself, don’t repeat the same task writing code a machine can automate. Step back from an everyday task and think about how you can make it simpler and easier. This is the DevOps revolution, write code and tools that automate the repetitive stupid tasks.

AI on log analyzer can really go through huge amounts of data and provide essential points about what happened and what’s going on.

Don’t be scared to use machines given the cost of the cloud to give you the data about the quality of your software

What’s next?

Helping large-scale organizations deal with challenges in four areas:

  • Overcoming critics – moving binaries from point A to point B.
  • Scalability with many endpoints devices and production sites.
  • Earning trust in the process and the pipeline throughout the organization.
  • Visibility – in charge and in control of the entire process.
devops ,automation ,software dvelopment ,jfrog

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}