Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I have a Docker app and currently have no backend (planning to make one in Spring Boot so it will be separated as microservices). Now, after my research, i have 2 options, I could push the app directly into S3 and set it as static web hosting without dockerizing it, or I could dockerize it and deploy it in ECS and still as a static web page. In my opinion, hosting it in S3 would be way easier, but what benefits or under what circumstances, it is best to dockerize my angular app and deploy it in ECS?
In my opinion, it is totally fine to host your static site on S3, but think about day 2 operations... How would you deploy new changes to the site? back up the site? revert to a specific version? of course, you can do all of it with scripting around S3 but it will require some effort... in my opinion building a container to serve static files is very simple and does not require more effort than creating the bucket, configuring it to serve static files, and add/create the required scripting/tooling to maintain and support the site. containers will win for me because of the ability to store and tag containers with specific versions(based on a specific commit) and better control over logs and debugging will win me. if it's a very low maintenance site go with a bucket otherwise I think it's worth containerizing it.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I have a personal website hosted on aws using s3, cloudfront and route53, but as time goes by I would like to have some dynamic functionalities such as allowing visitors to leave a private message. May I know what is the best option for me? Should I use an EC2 instance? Or Lambda + API gateway... etc?
Any suggestion is appreciated, thanks!
I would recommend that you start at Choose Your Web Application Infrastructure because there is no single answer.
There are different factors to take into account when deciding which service to use to deploy your first web application on the AWS Cloud. You should consider if you want a managed infrastructure with low stress, if you need containers (and why) or if you want full control and customization.
As I think you currently don't have server-side rendering type of setup that is great news for you to host a personal website, For any dynamic backend related stuff you can use AWS Lambda functions for contact forms submissions and other things and the price would also no very low to host these rather than switching to ec2
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I have been setting up several server side GTMs for my company in the last months. I have deployed both App Engine Flexible versions, as well as Cloud Run hosted ssGTMs.
I found using Cloud Run easier to setup and also cheaper as long as you stay under 300 million requests per month. Custom domain setup is also only slightly different.
The official documentation Basically only covers App Engine and Manual deployment.
I was wondering if there is any downside towards using Cloud Run for hosting your ssGTM besides potential cold starts (which I do not really care about).
I'm not very familiar with GTM but here are few things for using Cloud Run you have to figure out first.
Is GTM completley stateless ? Or does it needs State, Cloud Run doesn't offer a filesystem kind capabilities for storing files on disk
Is GTM already available as a container ?
You can avoid cold starts by setting the min replicas to 1 or higher so that there is at least always 1 instance available to serve traffic.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I am currently making an IoT device with an App. I had hired freelancers to make that App using Google Firestore since my IoT hardware is also connected to Firestore. The app was made using flutter and uses Firebase Authentication as well.
However, it has been suggested to me that AWS is a better solution for my IoT device, particularly because we were able to successfully connect our hardware to AWS, which was difficult for us to do using Cloud Firestore.
Now the challenge is: to change the App database. Since the project is at a nascent stage, our team can afford to use take some time to migrate from Firebase to AWS.
But my question is: how easy will it be for an app developer to change the database of an App that is partially made?
"Partially made" so I'm guessing the app is not in production. This reduces the difficulty.
Things that make migration hard.
Different types of database. If the aws database is not NoSQL (firestore is NoSQL), the difficulty is increased.
Data structure. Are the both data structures the same? if no, your developers will spend sometime transforming the data to the new structure.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Our Business Needs:
Want to launch a java based Web service
Need a mySQL database for the web application
We will need to run same web service securely for 10 different cuatomers
Our Plan:
Will go for EC2 service
We will use some application stacks having java / database and web server
Questions:
For the above services do we need all the three services EC2 / RDS and S3?
Can we prepare our Linux image with all the needs and upload it and tun it on S3?
Please help us with your valuable answers.
You're question is a little vague. You could do this all on 1 EC2 instance, depending on the load. You can install Java, and MySQL on a single linux instance. Weather this will work for you or not, depends on the app. load, the size of ec2 instance you use. Many things.
As for creating your own linux image, yes you can do this, there are many articles on the web detailing this, a quick google search turned up this one http://computeretal.blogspot.com/2010/05/create-amazon-machine-image-from.html
Good luck!
For the above 3 requirements, you can do this with just EC2 for the linux instances with Java web servers (Tomcat etc) and RDS for the MySQL (both of which are part of the free trial now).
You would only need S2 if you needed file storage.
You cannot premake the instances offline, you need to make them live.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have read a couple articles and I know the basic concept of cloud computing..But I still don't know what exactly I can do with this service.
As a mobile application developer, I have developed a couple of iPhone applications. I have a Bluehost account and I have MySQL database in there. I have a couple PHP scripts on my server and on device side, it sends http request to the server to get the data from database in XML format. That is basically how I designed and implemented my applications..
Now what can I do with a cloud computing? If I use a cloud computing service such as AWS then how it is going to change the structure of my application?
Thanks in advance...
Cloud computing doesn't necessarily have to change the structure of your app. The main benefit of cloud computing in a lot of cases is scaling.
Right now if your iPhone apps become really popular and overload your current host, what do you do?
Using the cloud, you could spin up new instances (servers) on demand almost instantly. Another benefit is you only pay for what you need. Of course, depending on the situation, it might require changes to your structure to take advantage of scaling features.
edit: Specific to AWS, they have a service called Elastic Load Balancing. Take a look: http://aws.amazon.com/elasticloadbalancing/