Improved Devops Roadmap. (#6998)
* Improved Devops Roadmap. * Apply suggested changes from @dansholds.pull/7008/head
Vedansh
3 months ago
committed by
GitHub
parent
992d817d1a
commit
a3422cd772
73 changed files with 216 additions and 105 deletions
@ -1 +1,17 @@ |
|||||||
# Artifacts |
# Artifacts |
||||||
|
|
||||||
|
Artifacts refer to the output of a build process, typically generated by a Continuous Integration (CI) tool. These outputs can be executable files, libraries, documents, or any other type of file that is produced as a result of building, compiling, or packaging code. |
||||||
|
|
||||||
|
## Artifacts can include |
||||||
|
|
||||||
|
- Compiled binaries (e.g., .exe, .dll, .jar) |
||||||
|
- Libraries (e.g., .so, .dll) |
||||||
|
- Packages (e.g., .zip, .tar.gz, .rpm) |
||||||
|
- Documents (e.g., .pdf, .docx) |
||||||
|
- Configuration files (e.g., .properties, .yaml) |
||||||
|
- Images (e.g., Docker images) |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@article@What are Artifacts - Oracle](https://docs.oracle.com/en-us/iaas/Content/devops/using/artifacts.htm) |
||||||
|
- [@article@What is an Artifact - Atlassian](https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/#:~:text=Artifacts%20are%20files%20that%20are,in%20a%20later%20deployment%20step.) |
||||||
|
|||||||
@ -1,4 +1,13 @@ |
|||||||
# Artifactory |
# Artifactory |
||||||
|
|
||||||
- [@article@Artifactory Website](https://jfrog.com/artifactory/) |
Artifactory is a universal DevOps solution for hosting, managing, and distributing binaries and artifacts. Any type of software in binary form – such as application installers, container images, libraries, configuration files, etc. – can be curated, secured, stored, and delivered using Artifactory. |
||||||
|
|
||||||
|
The name “Artifactory” reflects the fact that it can host any type of “artifact” needed in your software development “factory.” In software development, an artifact is any object produced during the software development and delivery process. Artifacts include the files used to install and run applications, as well as any complementary information necessary to configure or manage software. |
||||||
|
|
||||||
|
Artifactory serves as the central hub for your DevOps processes. All artifacts, dependencies, packages, etc. ultimately get put into and pulled from Artifactory. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@Artifactory Website](https://jfrog.com/artifactory/) |
||||||
|
- [@official@About - Artifactory](https://jfrog.com/blog/what-is-artifactory-jfrog/) |
||||||
- [@feed@Explore top posts about Artifactory](https://app.daily.dev/tags/artifactory?ref=roadmapsh) |
- [@feed@Explore top posts about Artifactory](https://app.daily.dev/tags/artifactory?ref=roadmapsh) |
||||||
|
|||||||
@ -1,4 +1,9 @@ |
|||||||
# AWS Lambda |
# AWS Lambda |
||||||
|
|
||||||
- [@article@AWS Lambda Introduction](https://docs.aws.amazon.com/lambda/latest/operatorguide/intro.html) |
AWS Lambda is an event-driven, serverless Function as a Service provided by Amazon as a part of Amazon Web Services. It is designed to enable developers to run code without provisioning or managing servers. It executes code in response to events and automatically manages the computing resources required by that code. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@AWS Lambda](https://aws.amazon.com/lambda/) |
||||||
|
- [@official@AWS Lambda Introduction](https://docs.aws.amazon.com/lambda/latest/operatorguide/intro.html) |
||||||
- [@feed@Explore top posts about AWS](https://app.daily.dev/tags/aws?ref=roadmapsh) |
- [@feed@Explore top posts about AWS](https://app.daily.dev/tags/aws?ref=roadmapsh) |
||||||
|
|||||||
@ -1,4 +1,9 @@ |
|||||||
# Azure functions |
# Azure Functions |
||||||
|
|
||||||
- [@article@Azure Functions Overview](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview) |
Azure Functions is a serverless solution that allows you to write less code, maintain less infrastructure, and save on costs. Instead of worrying about deploying and maintaining servers, the cloud infrastructure provides all the up-to-date resources needed to keep your applications running. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@Azure Functions - Serverless Computing](https://azure.microsoft.com/en-in/products/functions) |
||||||
|
- [@official@Azure Functions Overview](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview) |
||||||
- [@feed@Explore top posts about Azure](https://app.daily.dev/tags/azure?ref=roadmapsh) |
- [@feed@Explore top posts about Azure](https://app.daily.dev/tags/azure?ref=roadmapsh) |
||||||
|
|||||||
@ -1 +1,8 @@ |
|||||||
# Cloud Design Patterns |
# Cloud Design Patterns |
||||||
|
|
||||||
|
Cloud Design Patterns are a set of reusable, proven solutions to common problems that arise when designing and building applications for the cloud. These patterns provide guidance on how to design and implement cloud-based systems that are scalable, resilient, and efficient. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@](https://learn.microsoft.com/en-us/azure/architecture/patterns/) |
||||||
|
- [@article@What is CI/CD?](https://www.redhat.com/en/topics/devops/what-is-ci-cd) |
||||||
|
|||||||
@ -1 +1,10 @@ |
|||||||
# Cloud smith |
# Cloud Smith |
||||||
|
|
||||||
|
Cloudsmith is a cloud-native package management platform that enables organizations to manage and distribute software packages across their infrastructure. It provides a centralized repository for storing, managing, and deploying packages, making it easier to manage complex software dependencies and ensure consistency across environments. |
||||||
|
|
||||||
|
Cloudsmith supports a wide range of package formats, including Docker, Helm, npm, pip, and more. It also integrates with popular development tools like Jenkins, GitLab, and CircleCI, making it easy to automate package management and deployment workflows. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@Cloud Smith](https://cloudsmith.com/) |
||||||
|
- [@official@Cloud Smith Product Overview](https://cloudsmith.com/product/) |
||||||
|
|||||||
@ -1,4 +1,11 @@ |
|||||||
# Cloudflare |
# Cloudflare |
||||||
|
|
||||||
- [@article@Cloudflare Documentation](https://developers.cloudflare.com/) |
Cloudflare is a company that provides a range of services to help protect and accelerate websites and applications. At its core, Cloudflare is a content delivery network (CDN) and a reverse proxy cloud provider. This means that it acts as an intermediary between a website's origin server and its visitors, caching content and filtering out malicious traffic. |
||||||
|
|
||||||
|
Cloudflare was founded in July 2009 by Matthew Prince, Lee Holloway, and Michelle Zatlyn. The company was venture-capital funded and submitted its S-1 filing for IPO on the New York Stock Exchange in August 2019. It opened for public trading on September 13, 2019, at $15 per share. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [@official@Cloudflare](https://cloudflare.com/) |
||||||
|
- [@official@Cloudflare Documentation](https://developers.cloudflare.com/) |
||||||
- [@feed@Explore top posts about Cloudflare](https://app.daily.dev/tags/cloudflare?ref=roadmapsh) |
- [@feed@Explore top posts about Cloudflare](https://app.daily.dev/tags/cloudflare?ref=roadmapsh) |
||||||
|
|||||||
@ -1 +0,0 @@ |
|||||||
# Datadog |
|
||||||
@ -1,7 +1,7 @@ |
|||||||
# Design and implementation |
# Design and Implementation |
||||||
|
|
||||||
Good design encompasses factors such as consistency and coherence in component design and deployment, maintainability to simplify administration and development, and reusability to allow components and subsystems to be used in other applications and in other scenarios. Decisions made during the design and implementation phase have a huge impact on the quality and the total cost of ownership of cloud hosted applications and services. |
Good design encompasses factors such as consistency and coherence in component design and deployment, maintainability to simplify administration and development, and reusability to allow components and subsystems to be used in other applications and in other scenarios. Decisions made during the design and implementation phase have a huge impact on the quality and the total cost of ownership of cloud hosted applications and services. |
||||||
|
|
||||||
Visit the following resources to learn more: |
Visit the following resources to learn more: |
||||||
|
|
||||||
- [@article@Design and implementation patterns](https://docs.microsoft.com/en-us/azure/architecture/patterns/category/design-implementation) |
- [@article@Design and Implementation Patterns](https://docs.microsoft.com/en-us/azure/architecture/patterns/category/design-implementation) |
||||||
|
|||||||
@ -1,11 +1,24 @@ |
|||||||
# Docker |
# Docker |
||||||
|
|
||||||
Docker is a platform for working with containerized applications. Among its features are a daemon and client for managing and interacting with containers, registries for storing images, and a desktop application to package all these features together. |
Docker is a platform for working with containerized applications. Among its features are a daemon and client for managing and interacting with containers, registries for storing images, and a desktop application to package all these features together. Containers are lightweight and portable, providing a consistent and reliable way to deploy applications across different environments. |
||||||
|
|
||||||
|
## History |
||||||
|
|
||||||
|
Docker was founded in 2010 by *Solomon Hykes*, and the first version of Docker was released in 2013. Docker became an open-source project in 2014, and since then, it has gained massive popularity in the software development industry. |
||||||
|
|
||||||
|
## Key Features |
||||||
|
|
||||||
|
Docker provides several key features that make it an attractive choice for developers: |
||||||
|
|
||||||
|
- **Lightweight**: Containers are much lighter than virtual machines, making them faster to spin up and down. |
||||||
|
- **Portable**: Containers are portable across different environments, including Windows, Linux, and macOS. |
||||||
|
- **Isolated**: Containers provide a high level of isolation between applications, ensuring that each application runs independently without interfering with others. |
||||||
|
- **Efficient**: Containers use fewer resources than virtual machines, making them more efficient. |
||||||
|
|
||||||
Visit the following resources to learn more: |
Visit the following resources to learn more: |
||||||
|
|
||||||
- [@official@Visit Dedicated Docker Roadmap](https://roadmap.sh/docker) |
- [@official@Visit Dedicated Docker Roadmap](https://roadmap.sh/docker) |
||||||
- [@article@Docker Documentation](https://docs.docker.com/) |
- [@official@Docker Documentation](https://docs.docker.com/) |
||||||
- [@video@Docker Tutorial](https://www.youtube.com/watch?v=RqTEHSBrYFw) |
- [@video@Docker Tutorial](https://www.youtube.com/watch?v=RqTEHSBrYFw) |
||||||
- [@video@Docker simplified in 55 seconds](https://youtu.be/vP_4DlOH1G4) |
- [@video@Docker simplified in 55 seconds](https://youtu.be/vP_4DlOH1G4) |
||||||
- [@feed@Explore top posts about Docker](https://app.daily.dev/tags/docker?ref=roadmapsh) |
- [@feed@Explore top posts about Docker](https://app.daily.dev/tags/docker?ref=roadmapsh) |
||||||
|
|||||||
@ -1,3 +1,8 @@ |
|||||||
# Infrastructure Provisioning |
# Infrastructure Provisioning |
||||||
|
|
||||||
Tools in this category are used to provision infrastructure in cloud providers. This includes DNS, networking, security policies, servers, containers, and a whole host of vendor-specific constructs. In this category, the use of cloud provider-agnostic tooling is strongly encouraged. These skills can be applied across most cloud providers, and the more specific domain-specific languages tend to have less reach. |
Tools in this category are used to provision infrastructure in cloud providers. This includes DNS, networking, security policies, servers, containers, and a whole host of vendor-specific constructs. In this category, the use of cloud provider-agnostic tooling is strongly encouraged. These skills can be applied across most cloud providers, and the more specific domain-specific languages tend to have less reach. |
||||||
|
|
||||||
|
Learn more from the following resources: |
||||||
|
|
||||||
|
- [@article@Terraform Website](https://www.terraform.io/) |
||||||
|
- [@article@Azure Resource Manager Documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview) |
||||||
|
|||||||
@ -1,4 +1,8 @@ |
|||||||
# Serverless |
# Serverless |
||||||
|
|
||||||
|
Serverless computing, also known as Function-as-a-Service (FaaS), is a cloud computing model in which a cloud provider manages the infrastructure and dynamically allocates computing resources as needed. This allows developers to write and deploy code without worrying about the underlying infrastructure. |
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
- [@article@What is Serverless?](https://www.redhat.com/en/topics/cloud-native-apps/what-is-serverless) |
- [@article@What is Serverless?](https://www.redhat.com/en/topics/cloud-native-apps/what-is-serverless) |
||||||
- [@feed@Explore top posts about Serverless](https://app.daily.dev/tags/serverless?ref=roadmapsh) |
- [@feed@Explore top posts about Serverless](https://app.daily.dev/tags/serverless?ref=roadmapsh) |
||||||
|
|||||||
Loading…
Reference in new issue