Articles

In the software industry’s recent past, the biggest disruptive wave was Agile methodologies. While Site Reliability Engineering is still early in its adoption, those of us who experienced the disruptive transformation of Agile see the writing on the wall: SRE will impact everyone.

Any kind of major transformation like this requires a change in culture, which is a catch-all term for changing people’s principles and behaviors. As your organization grows, this will extend beyond product and engineering. At some point you also need to convince the key power-holders in your organization to invest in this transformation.

Source de l’article sur DZONE

Traditionally, testing has been perceived as a bottleneck in SDLC, something that causes delays in delivery. Organizations have long adopted the Agile/DevOps model, but not without its pitfalls and stumbling blocks, especially in achieving the ideal speed/quality balance.

For enterprise DevOps, it is vital to rethink testing approaches to achieve agility at scale. There is much of an overlap of roles, for instance between business analysts and QA testers. Is the tester’s role diminished because of this overlap or because of automation?

Source de l’article sur DZONE

If you’re paying attention to anything that’s happening in the development world, you’re likely familiar with the term “observability.” We’re seeing more and more monitoring companies from all different backgrounds jumping on the term to describe their solutions, many claiming their observability tool to be the factor that will take businesses to the next level.

Growing out-of-control system engineering, observability allows dev teams to unify and study the behaviors of various IT systems through the external outputs of the internal systems. In the case of software, that’s log events, distributed tracing, and time-series metrics. By unifying the data streaming through today’s complex IT environments, it certainly gives SREs and DevOps practitioners a leg up from traditional monitoring. But the data alone is no longer enough.

Source de l’article sur DZONE

I was in the first week of a new job and the assignment was to install a company software on the local machine. In the beginning, I found that there are some documents on the internal website which I could follow to install. This was a very optimistic expectation of course. As soon as I started reading and doing the steps, I realized that there are many things that are not mentioned in the document and I began to ask a lot of questions that I do not have any answers to. I had to ask the current DevOps engineers for each unclear part. Later, I found that every day I am on a call for hours with these engineers and we achieve bit by bit of this installation together. I would say 20% of the operations were documented and automated, but the rest of the things should be done manually. Finally, I managed to install the software in a week but still, there were many things I did not know how I had done, and forgot many other details that were not in the document. 

It turns out every time we have a new hire, this situation happens again and again and there has been no update neither on the document nor in the software installation process. What amazed me was that the DevOps engineers were proud of what they have already created after years but they did not realize that no one can install that software without them. This situation created a huge amount of complexity around the software deployment and takes hours for employees to figure out things again and again. So, no matter how nice all those scripts were, it created a high overhead for the company which was quite hidden for the managers for years. 

Source de l’article sur DZONE


Here at ShiftLeft, we are gearing up for Shifting Left: ’21, a one-day application security conference for developers and security practitioners on Jan 28, 2021. I’ve been a huge fan of security conferences ever since I attended my first security conference, NorthSec in Montreal. This time, I am excited to be on the organizer’s side and present this conference to you.

Shifting Left: ‘21 is entirely online and free to register here. Now let’s get into it! Here are the sessions that I am most excited about and that you should attend if you like machine learning, developing secure applications, or hacking into applications.

Source de l’article sur DZONE


Set Up Kubernetes Cluster

First, we need a Kubernetes cluster. You may use an existing one or set up a new one. For this tutorial, we chose to use GKE (Google Kubernetes Engine).

Just follow the quick start to create a cluster. To save your money, the default pool with only one node is sufficient for our testing. For node image type, use the default Container-Optimized OS; for machine type, please select one with at least 8G mem. After creating the cluster, go ahead to configure kubectl to connect to the cluster following this guide.

Source de l’article sur DZONE

You have probably read about Kubernetes, and maybe even dipped your toes in and used it in a side project or even at work. But understanding what Kubernetes is all about, how to use it effectively, and what the best practices are requires much more effort. Kubernetes is a big open-source project and ecosystem with a lot of code and a lot of functionality. Kubernetes came out of Google, but joined the Cloud Native Computing Foundation (CNCF) and became the clear leader in the space of container-based applications.

Let’s hear from Gigi Sayfan, author of the bestseller Mastering Kubernetes, Third Edition, about his methodologies and the approach he followed to create a powerful resource to acquaint learners all over the globe with the fundamentals and more advanced concepts of Kubernetes.

Source de l’article sur DZONE

In the « Using Heroku to Quickly Build a Multi-Tenant SaaS Product » article, I documented the foundation for a new SaaS solution that I am building (initially for my sister-in-law) — utilizing the Heroku ecosystem. Using Heroku allowed me to deploy the app quickly, without having to worry about infrastructure, DevOps, scalability when the app gets popular, etc. The « Integrating Twilio Into My SaaS Solution In Heroku » publication provided an example of how easy it is to create a Twilio instance and integrate the solution into my Fitness-based SaaS solution. This current journey has resulted in a feature set that both trainers and their clients have been able to enjoy.

This article is going to focus on invoicing clients for services that have been performed and will utilize messaging solutions within the Heroku ecosystem. The goals of the invoice process are as follows:

Source de l’article sur DZONE

We all love web badges. You might have spotted many of them in README of repositories, including the repository of my blog, The Cloud Blog. In general, web badges serve two purposes.

  1. They are visually appealing.
  2. They display key information instantly.

If you scroll to my website’s footer section, you will find GitHub and Netlify badges that display the status of the latest build and deployment. I use them to quickly check whether everything is fine with the world without navigating to their dashboards. In essence, a badge is an SVG image with dynamic content embedded in it.

Source de l’article sur DZONE