In today’s complex IT environments, integrating multiple systems through a single API is a common requirement. However, managing these integrations effectively requires the right middleware patterns. Middleware acts as the glue that binds different systems together, ensuring they can communicate and work as a unified system. But with so many middleware patterns available, choosing the right one for your use case can be challenging.
Devcontainers within Visual Studio Code (VS Code) is a powerful concept, being able to create a Docker container with all the tooling and runtime stacks a developer needs to work on a given project, without having to install anything but Docker, VS Code and the VS Code Remote Containers extension.
Beyond creating standard Azure DevOps Pipelines, we can use templates to manipulate a pipelines definition. We can make custom steps run before or after tasks, or add stages based on certain conditions, or choose to reject a pipeline if certain definitions may or may not exist.
Latest Posts
In today’s complex IT environments, integrating multiple systems through a single API is a common requirement. However, managing these integrations effectively requires the right middleware patterns. Middleware acts as the glue that binds different systems together, ensuring they can communicate and work as a unified system. But with so many middleware patterns available, choosing the right one for your use case can be challenging.
Devcontainers within Visual Studio Code (VS Code) is a powerful concept, being able to create a Docker container with all the tooling and runtime stacks a developer needs to work on a given project, without having to install anything but Docker, VS Code and the VS Code Remote Containers extension.
Beyond creating standard Azure DevOps Pipelines, we can use templates to manipulate a pipelines definition. We can make custom steps run before or after tasks, or add stages based on certain conditions, or choose to reject a pipeline if certain definitions may or may not exist.