top of page

Frequently Asked Questions

Find answers to commonly asked questions

  • What is DevOps?
    DevOps is the combination of cultural philosophies, practices, and tools that increase an organization's ability to deliver applications and services at high velocity: evolving and improving products faster than organizations using traditional software development and infrastructure management processes.
  • What is DevSecOps?
    Building on top of DevOps, DevSecOps stands for development, security, and operations. It's an approach to culture, automation, and platform design that integrates security as a shared responsibility throughout the entire IT lifecycle.
  • What are Containers?
    Containers are a form of operating system virtualization. The purpose of a single container may be to run anything from a small microservice or software process to a more extensive application. Inside a container are all the necessary executables, binary code, libraries, and configuration files.
  • What are Microservices?
    Microservices are small independent services that communicate over well-defined APIs. Building Microservices helps abstract implementation details from the whole organization while giving ownership to small, self-contained teams. The Microservices approach is more of an architectural and organizational strategy for software development. If done right, the Microservices architecture helps applications scale and grow much more quickly than a monolithic architecture.
  • What is Kubernetes?
    Kubernetes is a portable, extensible, open-source platform for managing containerized services that facilitates declarative configuration and automation. It has a large, rapidly growing ecosystem. Kubernetes services, support, and tools are widely available.
  • Why should I consider Stakater?
    At Stakater, our people and leadership have been involved in the DevOps space for the best part of a decade. We have been using Kubernetes from the early days and have been contributing to the Open Source community regularly. Our vision has always been to enable technology teams to focus on their strengths while we handle the operational side of things.
  • What are the different offerings by Stakater?
    Our offerings can be broken down into the following: Stakater's App agility platform (SAAP): Get a fully managed DevSecOps platform on the cloud for Kubernetes/OpenShift. Priced based on total number of nodes being utilized. Platform assessment: Assess your current maturity in the DevSecOps space with a two-three week engagement. Consulting: Customized services for your DevSecOps needs.
  • What is SAAP?
    SAAP stands for Stakater’s App Agility Platform, enabling developers to control and configure the entire cloud development loop to ship and scale software faster. SAAP helps companies stay through our curated list of standard and custom-built cloud-native tools, constantly monitored by our site reliability engineers.
  • Can I use specific tools without getting the whole SAAP package?
    Our add-on tools like Tronador and Tenant-Operator are not dependent on SAAP. You can use their specific functionality without needing to get the whole of SAAP.
  • What is an Environment?
    An Environment is a user-defined group that combines applications and all of the services and databases those applications require, running within a namespace. Environments typically represent the software project lifecycle stages, such as staging, development, QA, or production.
  • What is a Dynamic Test Environment?
    Dynamic Test Environment is a temporary/short term environment that is tied to the lifecycle of a single pull request or branch. It lets us test any changes before they get merged and deployed to a real/permanent environment
  • What does Tronador do?
    Tronador reduces the complexity of managing environments and enables developers to get back to building great products rather than worrying about how the machinery works.
  • Why should I use Tronador?
    How often have you asked, "Can I have a staging"? How many hours have you wasted maintaining and configuring environments? How about trying to develop or test applications, but without the full context (services and databases)? With the rise of microservices and the explosion in cloud technologies, environments are becoming more complex and with greater fault tolerance. All developers use environments, but only one engineer at a time can deploy to a staging environment due to constraints on shared environments.
bottom of page