These days, where many developers are working with containers and all their ‘outcomes’ are bundled in a Docker container, it is becoming challenging to manage and control them.
Moreover, as more containers and Kubernetes enter the party, the job gets that much harder. Now, you have a tool that can help you jump to the next level. The JFrog Container Registry is a new Docker, Helm, and generic registry that is scalable and reliable.
What’s even better? It’s free… and gives you some unique features you can’t find anywhere else.
Psychologist and Nobel laureate Daniel Kahneman reveals the actions we can take to overcome the biases. He talks in this podcast about the things that cripple our decision-making, damper our thinking, and limit our effectiveness.
Some gems from his conversion:
First one, is thought provoking as you take it to your personal or professional life.
“I think changing behavior is extremely difficult. There are a few guidelines about how to do that, but anybody who’s very optimistic about changing behavior is just deluded.”
A good API is like a classic car – You want to use it again and again.
Most of the interactions with Artifactory will be from your CI/CD tools. It might be your build engine or from your log aggregator. This powerful API can be invoked in any of the standard ways you like to work with any other RESTful APIs (e.g. curl, CLI, your source code, etc’). In many cases, it’s the preferred ‘glue’ for developers when it comes to automation. The options are extensive and you can do many useful things with this API. However, in this short post, we will cover the most popular actions you ‘must have’.
Let’s start with the most common action: “upload/download binaries“. This action could run automatically from the build machine to Artifactory using:
At last SwampUP, I had the opportunity to talk with Alan Shimel, Founder and Editor at DevOps.com. We covered what I do at JFrog and spoke about the definition of the role “VP of Technology”. We also covered some interesting new products we offering these days to help developers move faster.
I told Alan that I define the role as “finding leverage points in (JFrog) technology to support the business”.
The world has many buzzwords that people like to use. Some are more relevant to the real world and some aren’t. If yesterday was powered by new products and features, today is going to be filled by insights from our communities.
There are around 37 million developers in the world (according to GitHub last report) so it’s a substantial community. Moreover, DevOps is growing at a rapid pace. Btw, according to StackOverflow last survey – DevOps developers and site reliability engineers are among the highest paid, most experienced developers most satisfied with their jobs, and are looking for new jobs at the lowest levels.
I think we can all agree that data is stronger than opinions, rights? This is what I really like about the special point of view that we have at JFrog. As the “database of DevOps“, we are sitting in a unique place – holding the output of what developers producing. This is giving us excellent visibility into trends and the real world.
What does this mean?
It’s about contrasting perception with reality. We combined our own data from 5000 customers with internal and external researches in an effort to give you a clear picture of the current state and what are the DevOps trends for the next 12-18 months.
In the video below we talk about JFrog –Shippable acquisition and did our best to answer some of the questions, we got over the last couple of weeks.
What is Shippable?
Shippable provides software organizations with the ability to optimize and accelerate the process of shipping software by giving them an “Assembly Lines” platform that borrows concepts from the world of manufacturing and helps them easily achieve Continuous Delivery. Cutting-edge modern companies like Facebook, Amazon, Google, and Netflix have already built homegrown versions of Assembly Lines after spending years of effort and millions of dollars. You can ship applications as rapidly as these companies by leveraging Shippable.
JFrog
JFrog’s solution is a fully automated pipeline for distributing trusted software releases. It connects all developers and DevOps engineers to end devices and ensures software flows quickly and free from interruption. There are many good (starting) points of integration and it can be customized to the current needs of your company. For more about the enterprise platform read here: https://jfrog.com/enterprise-plus-platform/
If you wish to learn about Kubernetes, the first thing is to try it for yourself. Since many developers are using Mac, let’s see how to run it. This post is sort of a ‘checklist’ I wrote when I was first ‘playing’ with K8b… If you want more details please check the official site.
If you wish to see the power of docker on your Mac as a way to run all (or many) of your daily apps check this great post by Jess.
However, when you are going to the repo with all the Dockerfiles it’s clear that it was meant to be used on Linux. However, here is a short path to run all of these powerful apps on Mac as well.
Last week I had the pleasure to participate in a panel that talked about the future of DevOps. It was part of Transform!2019 Event that was in Munich, Germany. Fun fact, from the hotel I could see the Google office, which brought many good memories.
The main goal of the event was to let participants a way to experience what it means to change a company to become more “Intelligent”. The way to share the knowledge was by engaging in an open dialogue between industry leaders, start-ups in the DevOps world, executives and SAP experts. The event had few tracks and many options to network which was a great opportunity to learn from others.
DevOps Panel
When it comes to creating a business that can thrive in the digital age, the benefits of DevOps are clear. Faster deployment frequency and lower failure rates are proven to be some of the advantages of DevOps adoption. It brings more velocity into your (software) organization and enables you to add more value (faster) to your users.
Any developer knows that you must have a source code repository (e.g. Git) but from time to time I get the question “why do I need a binary repository”?
Here is the short answer:
Faster and more secure software development – Any company is a software company these days and the best companies release updates on daily/hourly bases. The ability to push updates quickly is a real competitive advantage. The minute you have few engineers on your team you wish to avoid ‘fetching the all internet’ with every ‘npm install’. A binary repo will give you the option to cache these libraries and make sure you are working with the correct ones (vs a hacked one). From the developer perspective, it is a big boost for their productivity as it saves time during development and on each build. Even better, from the DevOps perspective, the ability to control all the packages/libraries (and scan them for vulnerabilities) is a huge advantage. It enables the internal engineering team to control the releases better as they have full transparency (e.g. quality, performance, security, licenses, etc’) on everything the ‘compose’ the release version. Check the 12-factor app manifesto for more on dependencies (declaration and isolation).
Ido Green 