Skip to main content

Overview

In this section, you will find examples and use cases of StackSpot EDP.


This section provides various ways to use StackSpot EDP based on themes, journeys, and difficulty levels. Learn more below:

Journeys and Themes

The themes vary according to the usage possibilities and journeys within StackSpot EDP. See below:

Content Creator Journey

  • Where you create content: Studio and STK CLI.

The Content Creator is a developer specializing in establishing technological standards that are aligned with best practices and the future needs of the organization. These standards include Plugins, Stacks, Starters, and Workflows, and are designed to ensure scalable and practical solutions, promoting efficiency and collaboration. In addition to creating these standards, the Content Creator utilizes StackSpot to distribute them in a standardized and centralized manner within the Studios.

This approach allows the entire organization to access these solutions easily. For example, they can develop a Java or .NET Stack that incorporates best practices and essential tools for development, facilitating team workflows and optimizing internal processes. Their role is crucial in building a robust and sustainable technological ecosystem that supports business operations and fosters large-scale innovation.

Thus, the themes covered within this journey are:

  • Creating App Plugins;
  • Creating Infra Plugins;
  • Creating Stacks;
  • Creating Starters;
  • Creating Workflows.

Content User Journey

  • Where you use content: Workspace and STK CLI.

In StackSpot, the content user journey revolves around two main profiles: developers and Site Reliability Engineers (SREs). Both roles share the same goal: to ensure that solutions align with organizational standards and requirements while promoting efficiency, compliance, and resource reuse.

  • Developers: These individuals are responsible for creating and evolving applications within Workspaces, including APIs and internal systems. They utilize standardized content such as Stacks and Plugins. Developers configure integrated monitoring tools like Datadog and Grafana to track application performance, leveraging existing solutions while adding improvements or new features. This approach helps avoid duplication, accelerates development, and ensures that applications comply with organizational standards.

  • SREs (Site Reliability Engineers): SREs focus on creating and managing infrastructures within Workspaces, such as EKS clusters. They are responsible for ensuring the reliability and scalability of these resources. SREs use established standards to provision and monitor infrastructure, optimize operations, and promote resource reuse. Additionally, they collaborate to maintain the stability and efficiency of the technological ecosystem.

Together, these profiles complement each other, fostering an efficient and aligned technological ecosystem.

Thus, the themes covered within these journeys are:

  • Creating Applications;
  • Creating Infrastructures.

Difficulty Levels

The StackSpot EDP documentation is designed for users of all experience levels, ranging from beginners to advanced users. It explains how examples are structured according to each level's requirements: understanding the parameters that determine the difficulty levels of examples and use cases.

Beginner

The examples for beginners focus on those who are new to using StackSpot EDP and are still learning the basic concepts and tools.

  • Example: Create an Application with a Starter using the stk create app command.

Intermediate

Intermediate examples target users with some experience in StackSpot EDP who wish to explore more advanced features.

  • Example: Create an Infrastructure with customized Stacks and apply Infrastructure Plugins to provision cloud resources.

Advanced

Advanced examples target experienced users who wish to explore the full potential of StackSpot EDP.

  • Creating Stacks, Plugins, and Starters from scratch using development best practices. Examples of how to use Actions to automate complex workflows. Advanced configuration of Infrastructure resources like Lambda Authorizers.
  • Example: Create an Infrastructure Plugin that provisions a Kubernetes cluster and automatically configures access permissions.