AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
IONOS Hosting
Score 6.7 out of 10
N/A
IONOS a provider of cloud infrastructure, cloud services, and hosting headquartered in Germany, boasting more than eight million customer contracts. They provide individual web services including SSL certificates (provided by GeoTrust True BusinessID) , domain registration services, website hosting, and managed hosting services supporting WordPress, VPS hosting, and ASP.NET hosting.
N/A
Pricing
AWS Lambda
IONOS Hosting
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
No answers on this topic
Offerings
Pricing Offerings
AWS Lambda
IONOS Hosting
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Lambda
IONOS Hosting
Features
AWS Lambda
IONOS Hosting
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
I run five websites off of 1&1 for different outshoots of the company. For our web needs it works perfectly. We have a midgrade hosting package and it works perfectly. I know if issues arose from traffic or storage space 1&1 would have a solution for us.
Private registration: 1&1 offers free private registration which makes them an automatic favorite.
Reliable customer service: always someone available when I call in and I have never had my issue not get resolved.
Easy to use dashboard: domains in one place with DNS settings and other things that can be tweaked. It's easy to add an SSL certificate to domains as well.
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
The email system has not impeded out mail flow in any way, and we do not notice the delays we sometimes see with other systems that include spam/junk mail filtering.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
Rackspace I find to be too pricey for the service they offer. Pagely is very much WordPress oriented. I've had downtime with both that I haven't experienced with 1&1.
The scalability of the email solution far exceeds our needs and would be suitable for organizations not looking for an enterprise sized multipurpose solution (O365, Google Workspace, etc).
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.