Pros | Cons |
---|---|
Low impact deployment: can deploy a new version of the application with minimal impact on the users or the service availability | High complexity and testing challenges: need to de |
Pros | Cons |
---|---|
Zero-downtime deployment: can deploy a new version of the application without affecting the users or the service availability | High resource consumption and cost: need to have tw |
Best Practice | Description |
---|---|
Design your functions for statelessness | Serverless f |
| Problem | Explanation | Solution | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Best Practice | Description |
---|
Problem | Explanation | Solution |
---|
Best Practice | Description |
---|---|
Define clear goals and metrics for your canary deployment | Have a clear idea of what |
| Problem | Explanation | Solution
| Feature | Jenkins | GitHub | GitLab | Bitbucket | Circle CI | TeamCity | AWS CodeCommit | Cloud Source Repositories
Aspect | Bare Metal | Vitual Machine (VM) | Container |
---|---|---|---|
Hardware | Physical machines | Virtualized hardware | Shared hardware |
Hardware access | Full hardware access | Limited hardware access | Limited hardware access |
Performance | High and consistent | Moderate and variable | High and consistent |
Resource utilization | Low | Moderate | High |
Resource Usage | Dedicated resources | Shared resources | Shared resources |
Isolation | High (single tenant) | High (separate OS) | Moderate (shared OS kernel) |
Portability |