-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Azure links #2635
Update Azure links #2635
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I'd change the URLs from https://azure.microsoft.com/documentation/ to the new docs.microsoft.com URL. I've commented in a few cases, not all, but it should be easy to find them.
@@ -34,7 +34,7 @@ From an infrastructure perspective, each server can run many applications within | |||
|
|||
**Figure 4-2**. Monolithic approach: Host running multiple apps, each app running as a container | |||
|
|||
Monolithic applications in Microsoft Azure can be deployed using dedicated VMs for each instance. Additionally, using [Azure VM Scale Sets](https://azure.microsoft.com/en-us/documentation/services/virtual-machine-scale-sets/), you can easily scale the VMs. [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/) can also run monolithic applications and easily scale instances without requiring you to manage the VMs. Since 2016, Azure App Services can run single instances of Docker containers as well, simplifying deployment. | |||
Monolithic applications in Microsoft Azure can be deployed using dedicated VMs for each instance. Additionally, using [Azure VM Scale Sets](https://azure.microsoft.com/documentation/services/virtual-machine-scale-sets/), you can easily scale the VMs. [Azure App Service](https://azure.microsoft.com/services/app-service/) can also run monolithic applications and easily scale instances without requiring you to manage the VMs. Since 2016, Azure App Services can run single instances of Docker containers as well, simplifying deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -24,7 +24,7 @@ The following solutions are used to manage persistent data in Docker application | |||
|
|||
- Remote data sources like SQL or NoSQL databases, or cache services like [Redis](https://redis.io/). | |||
|
|||
- [Azure Storage](https://azure.microsoft.com/en-us/documentation/services/storage/), which provides geo-distributable storage, providing a good long-term persistence solution for containers. | |||
- [Azure Storage](https://azure.microsoft.com/documentation/services/storage/), which provides geo-distributable storage, providing a good long-term persistence solution for containers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -20,7 +20,7 @@ Enterprise applications can be complex and are often composed of multiple servic | |||
|
|||
In the container model, a container image instance represents a single process. By defining a container image as a process boundary, you can create primitives that can be used to scale the process or to batch it. | |||
|
|||
When you design a container image, you will see an [ENTRYPOINT](https://docs.docker.com/engine/reference/builder/) definition in the Dockerfile. This defines the process whose lifetime controls the lifetime of the container. When the process completes, the container lifecycle ends. Containers might represent long-running processes like web servers, but can also represent short-lived processes like batch jobs, which formerly might have been implemented as Azure [WebJobs](https://azure.microsoft.com/en-us/documentation/articles/websites-webjobs-resources/). | |||
When you design a container image, you will see an [ENTRYPOINT](https://docs.docker.com/engine/reference/builder/) definition in the Dockerfile. This defines the process whose lifetime controls the lifetime of the container. When the process completes, the container lifecycle ends. Containers might represent long-running processes like web servers, but can also represent short-lived processes like batch jobs, which formerly might have been implemented as Azure [WebJobs](https://azure.microsoft.com/documentation/articles/websites-webjobs-resources/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -64,17 +64,17 @@ Azure Service Fabric | |||
|
|||
![https://azure.microsoft.com/svghandler/service-fabric?width=600&height=315](./media/image26.png) | |||
|
|||
> [Service Fabric](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/) is a Microsoft microservices platform for building applications. It is an [orchestrator](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-cluster-resource-manager-introduction/) of services and creates clusters of machines. By default, Service Fabric deploys and activates services as processes, but Service Fabric can deploy services in Docker container images. More importantly, you can mix services in processes with services in containers in the same application. | |||
> [Service Fabric](https://azure.microsoft.com/documentation/articles/service-fabric-overview/) is a Microsoft microservices platform for building applications. It is an [orchestrator](https://azure.microsoft.com/documentation/articles/service-fabric-cluster-resource-manager-introduction/) of services and creates clusters of machines. By default, Service Fabric deploys and activates services as processes, but Service Fabric can deploy services in Docker container images. More importantly, you can mix services in processes with services in containers in the same application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- change https://azure.microsoft.com/documentation/articles/service-fabric-overview/ to https://docs.microsoft.com/azure/service-fabric/service-fabric-overview
- change https://azure.microsoft.com/documentation/articles/service-fabric-cluster-resource-manager-introduction/ to https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-resource-manager-introduction
> | ||
> As of May 2017, the feature of Service Fabric that supports deploying services as Docker containers is in preview state. | ||
> | ||
> Service Fabric services can be developed in many ways, from using the [Service Fabric programming models ](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-choose-framework/)to deploying [guest executables](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-deploy-existing-app/) as well as containers. Service Fabric supports prescriptive application models like [stateful services](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-services-introduction/) and [Reliable Actors](https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-actors-introduction/). | ||
> Service Fabric services can be developed in many ways, from using the [Service Fabric programming models ](https://azure.microsoft.com/documentation/articles/service-fabric-choose-framework/)to deploying [guest executables](https://azure.microsoft.com/documentation/articles/service-fabric-deploy-existing-app/) as well as containers. Service Fabric supports prescriptive application models like [stateful services](https://azure.microsoft.com/documentation/articles/service-fabric-reliable-services-introduction/) and [Reliable Actors](https://azure.microsoft.com/documentation/articles/service-fabric-reliable-actors-introduction/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
review the remainder https://azure.microsoft.com/documentation/ links to go to the new docs.microsoft.com link without en-us
@mairaw Ah ... yes ... np. These were all handled by script, and another little script will do the job. I'll take care of it. 🍰 |
@mairaw Script only found four lines in four files with this. Did I catch all of them looking for ...
|
There are still a couple left such as https://azure.microsoft.com/documentation/articles/websites-webjobs-resources/ |
I see. I only checked with a "services" segment ... I didn't address an "articles" segment. I'll get that on the next pass. |
@guardrex do you mean changing the docs.microsoft.com links to /azure? If so, these are ok like this because they're part of the microservices book. if we change them to relative links, then they can't use that as a source for a new edition as-is. |
Addresses Part 4 of #2580