Amazon DynamoDB vs. Azure Virtual Network

It’s great for server less and real-time applications. It would be great for gaming and mobile apps. However, if you need relational database and have fixed budget, do not use it. While budget can be managed, you need to be careful. Also this is not a tool for storing big data, there are other wide-column database types you could use for it ins the ad

For SAAS it's not required but for most of IAAS and PAAS components Virtual network are required the deployment of storage account doesn't require virtual network .

Incentivized

• To manage varying workloads, it enables users to increase capacity as necessary and decrease it as needed.
• Users can take advantage of its auto-scaling, in-memory caching, and backup without paying for the services of a database administrator.
• We can use it for low scale operations.

Incentivized

• Allows connectivity within Vnet
• Secure Communication can be established
• Security Rules can be enforced
• Routing Can be Established

Incentivized

• Cost model may not be easy to control and may lead to higher costs if not carefully planned
• Indexing may be a cost culprit when not planned, because it's not included on the data costs
• The Query Language may not fulfill everybody's expectations, as it has less features than those of competitors.

Incentivized

• Integration of Express Routes needs to be simplified
• Endpoints Security has to be available in Vnet itself

Incentivized

It's core to our business, we couldn't survive without it. We use it to drive everything from FTP logins to processing stories and delivering them to clients. It's reliable and easy to query from all of our pipeline services. Integration with things like AWS Lambda makes it easy to trigger events and run code whenever something changes in the database.

Incentivized

Functionally, DynamoDB has the features needed to use it. The interface is not as easy to use, which impacts its usability. Being familiar with AWS in general is helpful in understanding the interface, however it would be better if the interface more closely aligned with traditional tools for managing datastores.

Incentivized

It works very well across all the regions and response time is also very quick due to AWS's internal data transfer. Plus if your product requires HIPPA or some other regulations needs to be followed, you can easily replicate the DB into multiple regions and they manage all by it's own.

Incentivized

I have not had to contact support for this service, however I have had to contact AWS for other services and their support has been good.

Incentivized

The only thing that can be compared to DynamoDB from the selected services can be Aurora. It is just that we use Aurora for High-Performance requirements as it can be 6 times faster than normal RDS DB. Both of them have served as well in the required scenario and we are very happy with most of the AWS services.

Incentivized

During Initial Phase itself on cloud Journey Azure Services was opted for there was no comparison done

Incentivized

I have taken one point away due to its size limits. In case the application requires queries, it becomes really complicated to read and write data. When it comes to extremely large data sets such as the case in my company, a third-party logistics company, where huge amount of data is generated on a daily basis, even though the scalability is good, it becomes difficult to manage all the data due to limits.

Incentivized

• Some developers see DynamoDB and try to fit problems to it, instead of picking the best solution for a given problem. This is true of any newer tool that people are trying to adopt.
• It has allowed us to add more scalability to some of our systems.
• As with any new technology there was a ramp up/rework phase as we learned best practices.

Incentivized

• Deployment of Gateway needs to be faster as it takes a lot of time which is negative

Incentivized