More than 3000 questions in repository. There are more than 900 unanswered questions. Click here and help us by providing the answer. Have a video suggestion. Click Correct / Improve and please let us know.
Ans. Following are key differences between containers and serverless:
Supported host environments: Containers can run on any modern Linux server, as well as certain versions of Windows. In contrast, serverless runs on specific host platforms, most of which are based in the public cloud (like AWS Lambda or Azure Functions).
Self-servicing ability. For the reasons just noted, in most cases, serverless functions require you to use a public cloud. (There are on-premises serverless frameworks, like Fn, but these are not yet widely used.) With containers, you can set up your own on-premises host environment, or use a public cloud service like ECS.
Cost. Because serverless environments are hosted in the cloud, you have to pay to use them. In contrast, you can set up a container environment yourself using open source code for free (although you’ll still have management costs, of course).
Supported languages. You can containerize an application written in any type of language as long as the host server supports the language. Serverless frameworks are different; they support a limited number of languages. The details of supported serverless language vary from serverless platform to platform.
Statefulness. Most serverless platforms are designed to support stateless workloads. (Some serverless providers offer limited support for stateful services; cf. Durable Functions on Azure.) Although you can connect to external storage services (like S3 on AWS) from within serverless platforms, the functions themselves cannot be stateful. Containers present their own persistent storage challenges, but creating stateful containerized apps is certainly possible.
Availability. Serverless functions are designed to run for a short period—usually, a few hundred seconds—before they shut down. Containers can run for as long as you need.
Help us improve. Please let us know the company, where you were asked this question :
Ans. VPC stands for Virtual Private Cloud. You can define a VPC and subnets for a region in AWS and that can be used to access shared resources on the cloud. For eg: API gateway to access any file on S3.
Help us improve. Please let us know the company, where you were asked this question :
Ans. If instances in private subnet need to access internet without exposing the IP address to outside world , we use Nat gateway or nat instance. So there is a direct outbound traffic but not direct inbound traffic.
Help us improve. Please let us know the company, where you were asked this question :
More than 3000 questions in repository.
Discuss 
aws placement group
Asked in 3 Companies