review lab 1

Author: vermegi

docs/01_lab_plan/0102.md

@@ -14,6 +14,7 @@ The four primary options you will take into account are [Azure App Service](http
 * The Spring Petclinic application should be accessible via a public endpoint to any user (anonymously).
 * The new implementation of Spring Petclinic should eliminate the need to manually upgrade and manage the underlying infrastructure. Instead, the application should use the platform-as-a-service (PaaS) model.
 * Spring Petclinic implementation needs to adhere to the principles of the microservices architecture, with each component of the application running as a microservice and granular control over cross-component communication. The application will evolve into a solution that will provide automatic and independent scaling of each component and extend to include additional microservices.
+* Since you are starting from a Java Spring Cloud application, it would be nice to have in case any of the target services would provide you any out of the box Spring Cloud components.
 
 Consider any additional steps you may need to perform to migrate the Spring Petclinic application to the target service.
 
@@ -42,5 +43,6 @@ Fill out the following table based on your analysis:
 * AKS would require an extra migration step that involves containerizing all components. You will also need to implement Azure Container Registry to store and deploy your container images from or you could use a publicly available Docker repository.
 * Running and operating an AKS cluster introduces an additional effort.
 * Azure App Service scalability is more limited than AKS or Azure Spring Apps Service.
+* Both Azure Spring Apps and Azure Container App have built in components for Spring Cloud components. This will give you less services you'll need to deploy and operate.
 
-Given the above constraints and feature sets, in the case of the Spring Petclinic application, Azure Spring Apps and Azure Kubernetes Service represent the most viable implementation choices.
+Given the above constraints and feature sets, in the case of the Spring Petclinic application, Azure Spring Apps, Azure Kubernetes Service and Azure Container Apps represent the most viable implementation choices.

docs/01_lab_plan/0104.md

@@ -17,18 +17,18 @@ For information on how to organize your cloud-based resources to secure, manage,
 
 ## How will you configure networking for the application components?
 
-In case you chose to use Azure container apps, you do have an option to deploy it into your own virtual network or in microsoft managed vNet. If you use your own VNet, you need to provide a subnet that is dedicated exclusively to the Container App environment you deploy. And you need atleast /27 size subnet for the workload profiles and /23 for the consumption only plan.
+In case you chose to use Azure container apps, you do have an option to deploy it into your own virtual network or in microsoft managed VNet. If you use your own VNet, you need to provide a subnet that is dedicated exclusively to the Container App environment you deploy. You need at least a /27 size subnet when using workload profiles and a /23 size subnet when using the consumption only plan.
 
 In case you chose to use Azure Spring Apps, you have the option to deploy Azure Spring Apps either into a virtual network or deploy it without a virtual network dependency. The latter approach will simplify the task of making the first migrated version of the application accessible from the internet. Later on, in one of the subsequent exercises, you will change this approach to accommodate additional requirements. For now though, for the sake of simplicity, you will not create any virtual networks for Azure Spring Apps.
 
 In case you chose AKS as the hosting platform, you will need at least one subnet in a virtual network to run the nodes of your AKS cluster. This subnet for now can be small, such as `/26`, which allows for a total of 64 IP addresses (although some of them are pre-allocated for the platform use).
 
 The Azure Database for MySQL deployment will not require any virtual network connectivity for the first phase of the migration of the application. This will also change in one of the subsequent exercises, when you will implement additional security measures to protect the full application stack.
 
-
-
 ## Are there any supporting services you would need for running the application?
 
 In case you chose Azure Spring Apps, no additional supporting services are needed during the first phase of the migration. All you need is a compute platform and a database.
 
 In case you chose AKS, you will also need a container registry for storing any container images that will be deployed to the cluster. You can use for this purpose Azure Container Registry.
+
+For Azure Container Apps, you might need a container registry, depending on how you prefer to deploy your apps, this can be containerized and in that case you will need the container registry. Or, you can also choose to deploy from a jar file or from source code. In those latter 2 cases Azure Container Apps will handle the containerization for you.