This report provides a unique perspective on trends based on the usage of app architectures, processes, tools and use cases by leading-edge enterprises. The data in this report analyzes the technology adoption from more 2,000 Sumo Logic customers who run massive mission-critical modern applications on cloud platforms like AWS, Azure, and Google Cloud Platform, as well as hybrid cloud infrastructures.
The Amazon Web Services (AWS) Marketplace offers a large variety of commercial and open source offerings to augment software configuration and release within the AWS ecosystem. Sumo Logic's AWS Marketscape looks at the pros and cons of the most common configuration and release solutions from the Marketplace.
DevSecOps is the process and practice of development that makes every team member responsible for safety. By stressing a security-first, security-always approach as outlined in the DevSecOps Manifesto, DevSecOps incorporates security into the code level. DevSecOps builds infrastructure and applications that can securely scale at the speed of modern business.
Continuous integration is the practice of merging software code into an automated build process every time a new version is committed to source control. This triggers a series of automated tests that are performed before updates are added to the source code depository. In this way bugs, incompatibilities, and regressions can be identified and fixed rapidly—before they become a larger issue and disrupt workflow.
Continuous Delivery (CD) is a critical component of DevOps that can’t be overlooked. As you make the transition to CD, you need the right mindset, and the right tools. One tool that is indispensable if you host your apps in AWS is CodeDeploy. In this article, we look at why you would want to use a tool like AWS CodeDeploy, and how it doubles down on Continuous Delivery.
A key factor to automating feedback is telemetry. By inserting telemetric data into your production application and environment, the DevOps team can automate feedback mechanisms while monitoring applications in real-time. DevOps teams use telemetry to see and solve problems as they occur, but this data can be useful to both technical and business users.
Born out of open source collaboration, Docker helped revolutionize the software development world. By encasing software in shells of code called containers which included all the resources the software would need to run on a server—tools, runtime, system libraries, etc—the software can perform the same way across multiple hosting platforms. Docker’s container technology is at the forefront of mobile, scaleable development.
If you’re reading this article, you might be asking yourself what container orchestration engines are, what problems do they solve, and what are the differences between them. This article will attempt to give a high-level overview of Kubernetes, Docker Swarm, and Apache Mesos, as well as a few of their notable similarities and differences.
Kubernetes is an open-source container management system developed by Google and made available to the public in June 2014. The goal is to make deploying and managing complex distributed systems easier for developers interested in Linux containers. It was designed by Google engineers experienced with writing applications that run in a cluster.