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
Veeam Data Cloud for Microsoft 365
Score 8.8 out of 10
Mid-Size Companies (51-1,000 employees)
Veeam Data Cloud for Microsoft 365 is a BaaS (Backup as a Service) solution used to back up and restore Microsoft 365 data, including Microsoft Exchange, Microsoft SharePoint, Microsoft OneDrive for Business and Microsoft Teams data.
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.
Incredible tool for quickly setting up entire site backups for Microsoft 365 and Azure. One admin can support hundreds of user accounts easily, restoring files and emails takes minutes. Wording on how features work could be a bit more clear and the interface could do a bit more to have some tutorials baked in.
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.
Veeam Backup for Microsoft 365 just works so well and is so easy to use. I researched multiple options for Office 365 backup and none seemed to be as easy to setup and use as Veeam Backup for Microsoft 365 and the pricing was very comfortable to us. I can't imagine any reason why we would change away from Veeam Backup for Microsoft 365.
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.
Veeam Data Cloud for Microsoft 365 is very easy to use. You configure it, and it works. Reports can be configured to provide indepth details on backups and user licenses. I don't have to get into the panel unless I need to restore a backup. It has been a breeze to manage.
We have a lot of data, and pulling backups out of the store sometimes takes a bit of time - but this is within acceptable tolerances. I don't expect restores to be instantaneous, and I can't quantify if the speed is software or data repository.
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.
The setup support we received was extremely helpful. They allowed us to learn as they created the policies and managed the handoff between setup and guided setup very well. This resulted in active, usable policies and us having the knowledge to adapt these as our needs change in the future.
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
Veeam Data Cloud for Microsoft 365 is simpler to use then each alternative I've tried. Besides Synology, it's also the most cost effective. I also appreciate Veeam includes pricing on their website so I don't have to fill out a form or call someone. I don't like having to wait for a sales team to get back to me, and I don't want to have to deal with them after I decided on another product.
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.
The only real impact is from a compliance standpoint. Our company is expected at a regulatory level to be protecting our data and even though the tenant has little traffic there could still be some regulated data in there. We have to be able to tell an auditor that it's being backed up by an enterprise grade solution, and that's what VDC was intended for.
