Verbatim DVD Video Trimcases storage DVD jewel case
$34.38
$29.99
Mfg # 95094
CDW # 1054066
Quick tech specs
- Storage DVD jewel case
- black (pack of 50)
- capacity: 1 DVD
- for P/N: 43754, 97281, 97283, 97284, 97334, 97335, 97338, 97344, 97457, 97503, 97513, 97672
Know your gear
When it comes to storing and transporting DVDs and CDs, the choice is clear - Verbatim's DVD Video Trimcases are the answer. Verbatim's storage cases prevent your CDs and DVDs from being scratched or broken during transport. Verbatim's DVD Video Trimcases come in standard black and consume half the space of a standard Video Tall Box. These DVD Video Trimcases are ideal for storing favorite family movies and more.
Add to Compare
Enhance your purchase
Verbatim DVD Video Trimcases storage DVD jewel case is rated
4.50 out of
5 by
10.
Rated 5 out of
5 by
Michael Olayemi from
Provides free messages and helps to keep customers updated
What is our primary use case?
Within our organization, we handle procurement and keep customers updated through email. Most customers use our procurement application, which goes through different stages. When a customer submits a request on our website, we send them a message via Amazon WorkMail to confirm that their request has been received and is under review. We regularly update them on the status of their procurement through email.
For instance, if a customer is procuring items from China and shipping them to Africa, we inform them at each stage. From the initial procurement process in China to the transfer of goods to West Africa, such as Nigeria, we keep the customer informed at every step.
What is most valuable?
The most valuable feature of the Amazon WorkMail for me is the SMC server. It makes my work much easier, especially since I often work with Spring Boot. There are many built-in APIs in Spring Boot that help with messaging. What I appreciate about it is that it simplifies the process. I don't need to write much code; I define the credentials in my properties or environment variables. The Java Message API, an internal API from Spring Boot, does most of the work. I set up the properties and connected them to the SMC server, and I can send emails.
What needs improvement?
The solution is quite low-level and lacks some advanced features. For example, it doesn't provide tracking capabilities, such as knowing how many users opened an email, which is crucial for email marketing. You would need to integrate these analytics with other tools to get them. I need to know if there has been a bounce and how customers interacted with the email.
I would only suggest that Amazon WorkMail relax the rules for using Amazon SES in production. When you create an account, it starts in Sandbox mode, which means you can't use it in production right away. You must go through a process, message Amazon, and request to move it to production. Since Amazon is a big company, I feel customers shouldn't need this permission to use the service in production.
For how long have I used the solution?
I have been using the product for three years.
What do I think about the stability of the solution?
I rate the tool's stability a ten out of ten.
What do I think about the scalability of the solution?
I rate Amazon WorkMail's scalability a nine out of ten.
How are customer service and support?
I haven't had issues contacting Amazon support except when trying to move SES out of the sandbox environment. In my experience at different companies, the process varied. Getting approval to use SES in production at one company was straightforward, with just one message. However, at another company, it required multiple stages before approval.
How would you rate customer service and support?
Positive
How was the initial setup?
I rate the tool's deployment ease a ten out of ten. It is easy if your account is not in the sandbox. Integrating the code took as long as deploying Amazon SES. Once the code was live, Amazon SES was live. However, if we need to do a lot of configurations, like setting up NGINX and other things, the deployment can take up to 24 hours.
First, I make sure to have my credentials ready and push those credentials into the properties file. Since this is a Java application, I package the application into a WAR file. After packaging, I transfer the application to the server. Our running instance is usually attached to our server nodes. Once transferred, I start the service, and everything goes live.
You need one resource to handle the deployment. We don't need people to maintain this solution once it's deployed. It's very simple, and the chances of failure are very low. Most issues occur if someone adds an asset to the AWS account and removes the authentication credentials. If that doesn't happen, one person is enough to handle all the management tasks.
What was our ROI?
We can expect ROI with the tool's use. It improved our internal communication by replacing WhatsApp, which sometimes leads to unnecessary conversations.
What's my experience with pricing, setup cost, and licensing?
I rate the solution's pricing as one out of ten. It is close to being cheap. Sometimes, the tool offers a generous amount of free messages, up to 40,000, which is great for startups like ours. This means that we don't accumulate any costs for some months because we stay within the free usage tier. When we exceed the free allocation, the costs are reasonable, and no hidden charges exist.
What other advice do I have?
The tool is considered the industry standard for messaging services, and Amazon is well-known for being a leader in cloud technology. I rate it a ten out of ten. If your application involves sending many emails to customers, I highly recommend using Amazon WorkMail. It's straightforward and the best choice in my experience.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclaimer: I am a real user, and this review is based on my own experience and opinions.customer
Date published: 2024-07-12T00:00:00-04:00
Rated 5 out of
5 by
Mahender Nirwan from
Good integrations with Lambda functions, relationships with SNS, and other AWS services
What is our primary use case?
We use it to send emails, basically. Plus, whenever you send or receive an email, WorkMail gives you a trigger point. It's very much integrated with other AWS services. For example, one use case we had was with our UAT servers. They were costing us a lot because we had to pay for them every month, even when no one was using them for a few months.
So, we set it up so that whenever a client sends us an email saying "please turn on the UAT server," the UAT server automatically turns on using WorkMail. We get a trigger that the client wants the server on, so we turn it on. After four or five days, it automatically turns off, which saves us money. That's one use case we are using it for.
What is most valuable?
The integrations. WorkMail has great integrations with Lambda functions, relationships with SNS, and other AWS services. The integration capabilities are very simple, easy, and powerful.
With more integrations, you can create more workflows. If you have limitations, you cannot create those integrations.
What needs improvement?
WorkMail is not available in all AWS regions. It was not available in India, so I had to create a setup in Ireland. That was a limitation because I was trying to get a WorkMail account while being in India. I think it is supported now, but there might still be a few regions where it's not.
Integration can always be better. Plus, if more WorkMail agents are available for both India, that would be good. And if we have more WorkMail regions available, they can expect us to use more integrations.
For how long have I used the solution?
I have been using it for three to four years. I use the latest version.
What do I think about the stability of the solution?
It is very stable. I haven't faced any issues. We trigger about a thousand emails a day using Amazon SES, and we haven't faced any issues with availability.
What do I think about the scalability of the solution?
Our entire production service, even the test servers, relies on AWS. So, around one to 1.2 million users.
How are customer service and support?
The tech support is very much integrated. It's a single point of contact for support.
How was the initial setup?
WorkMail is not available in all AWS services. I'm not sure if it's available everywhere now, but I'm from India, and WorkMail was not available in India. I had to create a setup in Ireland. That was a limitation because I was trying to get a WorkMail account while being in the India region. The support team was working with us at that time. I think it is supported now, but there might still be a few regions where it's not supported.
The deployment takes wo to three days at large. Again, there's documentation. You can read it.
It's cloud-based.
What about the implementation team?
It can be done in-house. The standard AWS recommendations will also help with that.
What was our ROI?
The scalability and stability of SES and WorkMail are very great. If we use our own email servers or SMTP servers to send emails, we would always be worried about them going down. Sending an email is very important. If someone is sending notifications, it's crucial that people are aware of what is happening. So, having a perfect, scalable, and stable solution makes sense. And I see SES and WorkMail as one of the most scalable and stable solutions.
What's my experience with pricing, setup cost, and licensing?
It has a very good free tier. I think about 20,000 to 30,000 users are free. It has a great free-tier model. If you consume your free trial, then it will be charged on a per-email model. That is also very minimal. Overall, the pricing model is great.
What other advice do I have?
Overall, I would rate it an eight out of ten. If you are already on the AWS platform and deploying your services on AWS, using WorkMail for notifications through your application using SES makes a lot of sense because it is well-integrated with the entire system. If your emails get bounced, your application gets notified about it. Overall, if you are on the AWS cloud, you should use SES and WorkMail.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-08-19T00:00:00-04:00
Rated 5 out of
5 by
Victor Bergman from
It performs well, has good functionality, is easy to install, and is immediately activated
What is our primary use case?
We use WorkMail for email. You set up email accounts for various businesses. It is as simple as that. That is the purpose of WorkMail.
What is most valuable?
There is no need for me to set up security. This is also known as a platform as a service. Actually, I believe they are a software as a service (SaaS).
What needs improvement?
The only issue is the price, which is far too expensive.
For how long have I used the solution?
I have been working with WorkMail for three years.
What do I think about the stability of the solution?
WorkMail is a very stable solution.
What do I think about the scalability of the solution?
WorkMail is a very scalable product.
I'm currently transferring all of them away from WorkMail because it's too expensive.
How are customer service and support?
I would rate their technical support a zero out of five.
I have been trying to contact and reach them because they called me once but never returned my call.
They called to set up a meeting with me at Amazon, I believe for the South African level. And they never followed up on that meeting. I am just moving on, moving my clients away from them, and that's all that.
How would you rate customer service and support?
Negative
How was the initial setup?
The initial setup is straightforward.
It is deployed and activated immediately.
What's my experience with pricing, setup cost, and licensing?
WorkMail is very expensive. We have lost several clients because it is too expensive.
WorkMail is a bit expensive per user. That is something they must correct.
They provide excellent service, but it is expensive for South Africans. We are losing clients because the price my clients pay for email alone is nearly equal to the price they pay for an entire Microsoft Office license, which includes email.
Where they will have Microsoft Word and other productivity tools, as well as email. And you will pay nearly that much for an email with WorkMail. It's far too costly. That is unaffordable.
WorkMail does require a license, it is, per user. The license is for one user. It is costly per user. The license is expensive.
What other advice do I have?
I would recommend this solution to others who are interested in using it.
WorkMail works very well, and the functionality is fine. I would rate WorkMail a nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-08-14T00:00:00-04:00
Rated 5 out of
5 by
Hamed Khosrojerdi from
Solid security features and management but needs interface improvements
What is our primary use case?
I use Amazon WorkMail to create email accounts and integrate them with Gmail and Microsoft Outlook. I've launched a website and migrated it to AWS infrastructure, and WorkMail is part of this integration.
How has it helped my organization?
Amazon WorkMail integrates with Route 53 and other AWS services, providing a seamless experience when using AWS infrastructure.
What is most valuable?
Amazon WorkMail's positive points include its security, user management, and organization and categorization features offered by the management console.
What needs improvement?
Amazon WorkMail's user interface could be more intuitive and user-friendly. Integration with Gmail using both SMTP and POP3 would be beneficial.
For how long have I used the solution?
I have been working with Amazon WorkMail for about seven months.
What do I think about the stability of the solution?
I have not experienced any problems with the stability of Amazon WorkMail.
What do I think about the scalability of the solution?
Amazon WorkMail is highly scalable, similar to other services offered by AWS, and is one of its most important features. However, with only two users currently, I cannot comment further on its scalability.
How are customer service and support?
I have not contacted technical support for Amazon WorkMail.
Which solution did I use previously and why did I switch?
Before using Amazon WorkMail, we used Bluehost as a cost-effective provider for email services, which was cheaper than AWS. However, the features provided by AWS were beneficial.
How was the initial setup?
The initial setup of Amazon WorkMail took about an hour and involved learning through various tutorials due to the complex management console.
What about the implementation team?
I deployed and maintained the solution myself, without any external help.
What's my experience with pricing, setup cost, and licensing?
I pay four dollars per month for each user of Amazon WorkMail. I believe the price could be cheaper given the features provided.
Which other solutions did I evaluate?
I did not evaluate other solutions before choosing Amazon WorkMail.
What other advice do I have?
Currently, I don't have any advice about using Amazon WorkMail. Since I only use AWS and am unfamiliar with its competitors, I can't recommend it.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.customer
Date published: 2024-10-15T00:00:00-04:00
Rated 5 out of
5 by
Ravi Satyanarayana from
Highly reliable and scalable, completely managed, and helpful support
What is most valuable?
Three main things that I like about it are:
* It comes out of the box as an Amazon service.
* It is completely a managed solution.
* It is highly scalable.
Because it is completely managed, I don't need to worry about availability and resiliency. These are the things that we typically require from any email service. We previously had a lot of problems with the on-premise environment.
It is highly available and scalable. It is also highly reliable. I don't lose any of the messages or emails. If there is an issue where the email sent operation failed, Amazon as a platform ensures that the send operation is retried, and the email reaches its destination. This way, it is highly reliable.
What needs improvement?
Email service is definitely a requirement from an enterprise standpoint. Many organizations have their own on-premise email services, which take a lot of memory, backup, and other resources. If we can have a completely managed backup solution where we have a tiered backup or a tiered archival to be able to retrieve emails, it would be great. I would like to be able to retrieve emails in real-time (hot retrieval), over the 90-days period (warm retrieval), and over the one-year period (cold retrieval). It would be useful to have tiered backup and retrieval. It would help us in managing emails better and have a better backup solution. So, backup is something that we require.
We would also like to have cross-regional support. Tomorrow, my enterprise might be functioning across multiple geographies or globally, and if we can have a sustainable and reliable synchronization solution to replicate emails across multiple geographies so that everybody can access them—if not in real-time, then at least in a suitable amount of time—it would be helpful. It would be a really good feature to add.
For how long have I used the solution?
I have been using it for about a year and a half.
What do I think about the stability of the solution?
It is definitely stable. There is no doubt about it.
What do I think about the scalability of the solution?
It is highly scalable.
How are customer service and support?
They were very friendly and helpful. We were able to get some of the queries resolved on the fly. We had posted a few things on the Marketplace as well. Sometimes, we had to connect with our Alliance partners to deal with some of the issues, and we were able to get good support within the defined SLAs, which was really good.
What other advice do I have?
I would definitely recommend this solution to others. I would rate it an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-04-13T00:00:00-04:00
Rated 5 out of
5 by
Poulav Biswas from
SES has strong deliverability rates, ensuring that emails sent through the service reach their intended recipients' inboxes
What is our primary use case?
Our use case for sending out broadcasts and emails through our CRM.
What is most valuable?
The most valuable thing is that emails sent through SES have a delivery rate of greater than ninety percent. It's a big factor in gaining trust in Amazon, as most of the time, they land in the inboxes.
What needs improvement?
There is room for improvement in the support. It's just that customer support, though good, takes time to resolve issues.
For how long have I used the solution?
I have been using Amazon SES for more than a year. We currently use the latest version.
What do I think about the stability of the solution?
I would rate the stability a nine out of ten. It is a stable solution.
What do I think about the scalability of the solution?
I would rate the scalability a nine out of ten.
How are customer service and support?
There is room for improvement in support.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is moderate, neither easy nor too hard. The deployment took me two to three hours.
What's my experience with pricing, setup cost, and licensing?
It's very cheap. The cheapest among all the services available.
What other advice do I have?
It's pretty complicated and not that easy to set up. But, in the long run, it's very helpful. It gives successful outcomes out there.
Overall, I would rate the solution a nine out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-26T00:00:00-04:00
Rated 5 out of
5 by
Rastu Singh from
Reliable with good deliverability and the ability to expand
What is our primary use case?
We primarily use the solution for:
* Transactional emails. Applications can use SES to send emails related to specific user actions, such as password resets or account confirmations.
* Marketing emails. SES can be used to send newsletters, promotional emails, and other marketing communications to large email lists.
* Notification emails. SES can be used to send notifications or alerts to users or administrators, such as order confirmation emails or system status updates.
* Custom emails. SES can be used to build custom email solutions, such as automated email responses or personalized email campaigns.
Overall, SES is designed to make it easy for businesses to send a high volume of emails quickly and reliably, with features like automatic retries and email-sending history tracking.
How has it helped my organization?
The solution has improved our organization by offering:
* Scalability. Amazon SES can handle a high volume of emails, making it suitable for organizations with large email lists or that need to send a large number of emails on a regular basis.
* Deliverability. SES uses machine learning and other techniques to help improve the deliverability of emails, increasing the likelihood that emails will be delivered to their intended recipients.
* Reliability. SES has a 99.9% availability rate and automatically retries failed deliveries, helping to ensure that emails are delivered successfully.
* Integration. SES can be easily integrated with other AWS services and third-party applications, allowing organizations to build custom email solutions or integrate email communication into their existing systems.
What is most valuable?
The most valuable aspects of the solution are:
* Machine Learning. SES uses machine learning and other techniques to help improve the deliverability of emails, increasing the likelihood that emails will be delivered to their intended recipients.
* Integration. SES can be easily integrated with other AWS services and third-party applications, allowing organizations to build custom email solutions or integrate email communication into their existing systems.
* Automation. SES offers features like automatic retries and bounce, and complaint handling, which can help to automate some email management tasks and improve the efficiency of an organization's email communication.
* Security. SES includes features like DomainKeys Identified Mail (DKIM) signing, email encryption, and authentication to help protect the security of emails and the reputation of an organization's domain.
* Cost. SES offers a pay-as-you-go pricing model, so organizations only pay for the emails they send, helping to control costs.
What needs improvement?
We'd like to see the following improvements:
* A/B testing. The ability to create and send multiple versions of an email to a small subset of an email list and then use data on which version performed better to inform future email campaigns would be helpful.
* Email scheduling. We need the ability to schedule emails to be sent at a specific date and time in the future rather than being sent immediately.
* Email personalization. We'd like the ability to insert personalized elements like a recipient's name or location into emails using data from an organization's systems.
* Advanced analytics. It would be ideal to have detailed data and reporting on email opens, clicks, bounces, and other metrics, as well as integration with other business intelligence tools.
* Advanced spam filtering. We need additional spam filtering options beyond the basic spam filtering already provided by SES, such as blocking specific types of content or customizing the spam filter's thresholds.
For how long have I used the solution?
I've been using the solution for five years.
Which solution did I use previously and why did I switch?
As an email infrastructure and deliverability expert, I have to choose multiple solutions based on the needs of an organization.
Which other solutions did I evaluate?
We always compare the solution with Sendgrid, Sparkpost, Mailchimp, Mailgun, etc., and based on the requirements, provide the solutions.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-01-09T00:00:00-05:00
Rated 5 out of
5 by
Ali Asad from
Helps in transactional emails and marketing but need detailed reports on email success and failure rates
What is our primary use case?
We use the tool for transactional emails and marketing.
What needs improvement?
I would like to see detailed reports on email success and failure rates.
For how long have I used the solution?
I have been using the product for a year.
What do I think about the stability of the solution?
Amazon SES is stable.
What do I think about the scalability of the solution?
We use the solution daily.
How are customer service and support?
I haven't contacted technical support yet.
How was the initial setup?
I rate Amazon SES's deployment a ten out of ten. It takes 30-40 minutes to deploy. One person helped us with the deployment.
What about the implementation team?
We did the tool's deployment in-house.
What other advice do I have?
I rate the overall product an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-02-03T00:00:00-05:00
Rated 5 out of
5 by
Prasanth MG from
A stable solution used to send emails and notifications to customers
What is our primary use case?
We use Amazon SES to send emails and notifications to our customers.
What is most valuable?
Amazon SES is very easy to configure. If I have an email ID in Gmail, I would have to learn the Gmail API to send an email programmatically. The advantage of Amazon SES is that I don't have to learn the API of the email service provider. I can just add my email on Amazon SES, do some verification, and send the email content directly to Amazon SES, which will then go through my email. So I don't have to learn the API of the email service provider. If tomorrow we start using a Yahoo account, I'll have to learn the API of the Yahoo email service. So, in this case, we can add both accounts to Amazon SES, and we only have to learn the API of Amazon SES.
What needs improvement?
When we first set up an email on Amazon SES, they had to verify it, which was not fast enough.
For how long have I used the solution?
My senior has been using Amazon SES for more than one year, but I started using it around six months ago.
What do I think about the stability of the solution?
Amazon SES is a stable solution, and we haven't faced any bugs.
What do I think about the scalability of the solution?
Amazon SES is a scalable solution. Three people use the solution in our organization.
How was the initial setup?
The solution’s initial setup is very easy.
What other advice do I have?
We chose Amazon SES because it was the recommended serverless service.
Other than Amazon SES, there isn't another alternative within AWS.
Overall, I rate Amazon SES ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-06-30T00:00:00-04:00
Rated 5 out of
5 by
Rahul Siddu from
provides verified email messages, ensuring a higher level of trust and stable for small and medium-scale usage
What is our primary use case?
Our primary use case is to send emails to any person using an identity.
What is most valuable?
The best feature is that Amazon SES provides verified email messages. There are many software and email services, but SES provides verified accounts for an organization. With SES, you can also handle any bounces or complaints we receive from emails.
What needs improvement?
There is room for improvement in the scalability. Currently, you can only send one notification at a time. It would be great if it could send to multiple recipients simultaneously using different email addresses.
For example, in one organization, different departments like HR and engineering can use one identity each to send emails. This would make it more scalable and stable.
In future releases, I would add the ability to send multiple messages at the same time using different domains within the same company.
For how long have I used the solution?
I have been using Amazon SES for the past four to five months.
What do I think about the stability of the solution?
Currently, for small and medium-scale usage, it's very stable.
What do I think about the scalability of the solution?
Probably less than 20 to 30 percent of the workforce uses AWS in our organization.
How was the initial setup?
If you have an AWS account, the initial setup is easy.
What other advice do I have?
I would recommend it because it is a very secure service.
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-06-29T00:00:00-04:00