In three weeks, I managed to deploy the services that I wanted. Out of the four services I deployed, three of them went just fine. The fourth one was more problematic because it was deployed successfully on the tenth attempt. It needs some customizations because it's more complex. Build processes rely on external factors that need to be adjusted so that they would run within the boundaries of AWS App Runner. AWS App Runner provides an easy way to deploy higher-level compute services instead of individually managing compute instances of EC2 service. EC2 are virtual machine boxes that you can start and stop whenever you want to. If you also automate some kind of monitoring on those instances and put a load balancer above it, you are managing your automation manually. However, if you need a simpler website or service deployment, you would typically want to try to utilize some kind of managed service that AWS manages for you, and you are paying by a different scheme. You are not paying upfront for the number of hours your machines are running, but you are charged for the value you get from the service. That's where the managed service is sometimes preferable if you want to optimize the value you get from AWS services. That's why I decided to try those. They were really easy to start with, which is also interesting. When you have a vast sea of choices, it's a good idea that you could experiment and try your own things. Some things get started much faster than others. AWS App Runner was okay for my purposes. They have some kind of phase when you're consuming the services. However, they also have a separate phase when you're building or working through the service. You typically write your source code somewhere. You also write a lot of procedures, like what to do with the source code, what your DevOps processes are, or what your data pipelines are that should convert the data in the format you need. I'm running some of those in the cloud automatically or in some batch processes. I'm running the others on the workstations that I'm using. Those workstations can be physical or remote. The desktop service runs in the AWS cloud. There is a service called workspaces, and if you spin up a workspace in the AWS cloud, you can tell it to do different batch processes. This is another way to run those remotely. Sometimes, preparations for those processes can be done at the front end, on the workstations, and not at the servers of the underlying cloud. That's why it's hybrid. I would recommend the solution to other users because it's very well-targeted where we all need to be. You'd like everything to work out and spend less time with the inner workings, and it's doing this job just perfectly. Three of the four services work out of the box very easily. The fourth one has problems, which means that even AWS App Runner is not perfect. I'm sure that the problems are not connected to the solution itself. The source code I've been trying to give it to deploy has some issues that must be addressed. It has been optimized for another platform and not for the AWS cloud. If you optimize it for the AWS App Runner service, it should work out of the box again, but it will take some time. Overall, I rate the solution ten out of ten.
Development Platforms enable software creation by providing essential tools, libraries, and frameworks. These platforms streamline the development process, enhancing productivity and reducing time-to-market.
Development Platforms are instrumental in today's digital landscape, offering a range of functionalities from coding assistance to deployment and maintenance tools. They cater to different types of developers, from beginners to professionals, making the software development...
In three weeks, I managed to deploy the services that I wanted. Out of the four services I deployed, three of them went just fine. The fourth one was more problematic because it was deployed successfully on the tenth attempt. It needs some customizations because it's more complex. Build processes rely on external factors that need to be adjusted so that they would run within the boundaries of AWS App Runner. AWS App Runner provides an easy way to deploy higher-level compute services instead of individually managing compute instances of EC2 service. EC2 are virtual machine boxes that you can start and stop whenever you want to. If you also automate some kind of monitoring on those instances and put a load balancer above it, you are managing your automation manually. However, if you need a simpler website or service deployment, you would typically want to try to utilize some kind of managed service that AWS manages for you, and you are paying by a different scheme. You are not paying upfront for the number of hours your machines are running, but you are charged for the value you get from the service. That's where the managed service is sometimes preferable if you want to optimize the value you get from AWS services. That's why I decided to try those. They were really easy to start with, which is also interesting. When you have a vast sea of choices, it's a good idea that you could experiment and try your own things. Some things get started much faster than others. AWS App Runner was okay for my purposes. They have some kind of phase when you're consuming the services. However, they also have a separate phase when you're building or working through the service. You typically write your source code somewhere. You also write a lot of procedures, like what to do with the source code, what your DevOps processes are, or what your data pipelines are that should convert the data in the format you need. I'm running some of those in the cloud automatically or in some batch processes. I'm running the others on the workstations that I'm using. Those workstations can be physical or remote. The desktop service runs in the AWS cloud. There is a service called workspaces, and if you spin up a workspace in the AWS cloud, you can tell it to do different batch processes. This is another way to run those remotely. Sometimes, preparations for those processes can be done at the front end, on the workstations, and not at the servers of the underlying cloud. That's why it's hybrid. I would recommend the solution to other users because it's very well-targeted where we all need to be. You'd like everything to work out and spend less time with the inner workings, and it's doing this job just perfectly. Three of the four services work out of the box very easily. The fourth one has problems, which means that even AWS App Runner is not perfect. I'm sure that the problems are not connected to the solution itself. The source code I've been trying to give it to deploy has some issues that must be addressed. It has been optimized for another platform and not for the AWS cloud. If you optimize it for the AWS App Runner service, it should work out of the box again, but it will take some time. Overall, I rate the solution ten out of ten.