We recently released the automated Falco rule tuning feature in Sysdig Secure. Out-of-the-box security rules are a double-edged sword. On one side, they allow you to get started right away. On the other, it can take many working hours to learn the technology, configuration, and syntax to be able to customize the rules to fit your applications. Falco’s default security rules are no different.
Yesterday, my morning started much like most Tuesday mornings do for me... my kids (6 and 4) were up way too early again at around 6am! Both were demanding I play with them before they head to school. I did my usual and said "give me five minutes" as I tried to wake up after another night of going to sleep after midnight... one day I should really learn to go to bed earlier, now that I have kids! But this morning was different. I started to wake from my dazed state and reached for my phone.
Kubernetes just turned 7 years old, and over the last couple of years, it has risen in popularity to be the key platform for microservices management consistently. The ecosystem around it is also growing rapidly.
The way we architect and build applications has changed over the last decade or so. Where monoliths (or single, large codebases) used to be the standard, modern applications are now built using a combination of new architecture patterns, operational models, and software delivery services.
Nowadays APIs are the de facto method of communication between services. With all the connections points, setting up environments to efficiently build and test can be difficult. Also, in lower environments, 3rd party APIs can be unreliable, incorrect or non-existent.
In a relatively short amount of time, Kubernetes has evolved from an internal container orchestration tool at Google to the most important cloud-native technology across the world. Its rise in popularity has made Kubernetes the preferred way to build new software experiences and modernize existing applications at scale and across clouds. With Kubernetes, companies can host workloads running on a single cloud, as well as workloads across multiple clouds.
In a previous post, we discussed the rise of the developer platform and how developer productivity is one of the main reasons why many organizations are either looking for or building an internal developer platform (IDP). According to a recent global survey done by Stripe, on a scale of 0 – 100%, developers responded that only 68.4% of their time is productive, which means that developers could be nearly 50% more productive than today: (100% — 68.4%) / 68.4% = 46%
For the last several years, GitLab has run a major survey about the trends facing the DevSecOps community. This year over 4,000 people responded to the survey, 40% who identified as a Software Developer / Software Engineer. Also about half the survey participants are based in Asia, a major region for Software Developers. One of the biggest trends you will find throughout the survey is how much developers value speed and efficiency.
Docker containers have revolutionized the cloud industry. While Docker containers already present remarkable benefits and plus-points over other virtualization methods, there are significant performance gains that developers can further squeeze out of Docker to get the most out of the technology. This guide will cover different methods of optimizing Docker performance and answer some frequently asked questions about the technology.
