Is there any difference between Azure redis cache and redis.io , If I have Azure Subscription, I need to purchase seperate plan for Azure Redis.
IF have a difference ? When to Use Azure redis vs Redis.io.
Azure Redis Cache is a Managed Azure service, which creates and manages the Redis instance(s) (updates, automatic failover etc.) on behalf of the customer and provides the customer with TCP endpoint(s) to communicate with. It ultimately consists of one or more instances of Redis (as described in redis.io) server, however the customer doesn't have access to the physical VMs as the service is a managed service. Various management operations are available via the Azure portal or the Management interfaces. Details are here: Azure Redis Cache sevice.
There shouldn't be any difference in Redis functionality between what you see on redis.io and the Azure Redis service.
Once you have an Azure subscription, you pay for the Azure services that you use based on their pricing. The pricing details for the Azure Redis Cache service are here: Azure Redis Cache Pricing
Related
This is regarding the use case where we are trying to use the Redis in PCF (Pivotal Cloud Foundry). In our use case, we will refresh the Redis cache daily once or twice with the required data and then API will query Redis and then provide the response.
One thing of particular concern for us is that we want API queries to happen from Redis only that means Redis to be available at all times. But whenever we are refreshing the Redis DB, Redis would not be able to serve the APIs since it is refreshing the keys. To avoid that we wanted to setup a Redis in cluster mode or master-slave mode so if one instance is being written another can be read from.
How can we setup Redis cluster or master-slave mode in PCF and then fulfil our requirement?
Please provide any other suggestions as well that you may have.
At the time I write this, the Redis for Pivotal Platform product does not support clustering. See Availability, in the docs here -> https://docs.pivotal.io/redis/2-3/erc.html#offerings.
All Redis for Pivotal Platform services are single VMs without clustering capabilities. This means that planned maintenance jobs (e.g., upgrades) can result in 2–10 minutes of downtime, depending on the nature of the upgrade. Unplanned downtime (e.g., VM failure) also affects the Redis service.
Redis for Pivotal Platform has been used successfully in enterprise-ready apps that can tolerate downtime. Pre-existing data is not lost during downtime with the default persistence configuration. Successful apps include those where the downtime is passively handled or where the app handles failover logic.
If you require clustered Redis, you'd need to look at a different offering. Redis Labs has some offerings that integrate with PCF, you could use a Cloud Provider's Redis offering, or you could host your own.
If the solution you use isn't integrated into PCF, you can create a user-provided service with cf cups and provide the Redis credentials to your application that way. It will function just like a Redis service instance created through the marketplace.
We have checked both Redis installed in Azure VM and Azure Redis Cache both are working same I can't see a difference in the performance Have anyone used both in large scale application if so can anyone share the performance and durability of both ?
Have analysed the following
Monitoring
In-zone replication
Multi-zone replication
Auto fail-over
Data persistence
Backup
Pricing
SSL Authentication & Encryption
All the above Azure redis have the upper hand
Still I want make sure which one is the best
Does using VM has any bottlenecks ?
I would go for Azure Redis Cache. Mainly because its fully managed. At the end of the day you do have nodes under the hood. But why should you care for maintaining a VM? Hotfixes? Patches, Seucirty Updates ..etc ..etc.
I would ask the question the other way around. Why should you use VMs at all?
MG
I wanted to share some data to every worker in a swarm cluster.what are the possible methods to do the same.The swarm was created from docker cloud with azure integration.
Can I attach a single data disk to all worker VM's in an azure swarm cluster?
adding a single datadisk to all worker VM's is not possible. As Azure is not able to provide a 'shared disk' facility. The only things which comes close to it is the usage of Azure Files see herr --> https://learn.microsoft.com/en-us/azure/storage/storage-how-to-use-files-linux
for further details
Is it possible to enable the Geo-Replication in an already running VM?
How we can make sure that Geo-Replication is working?
Is there any other option for securing the Data safe?
You have to enable geo replication on your storage account associated with your VM (Azure storage account you used while creating the VM). You can enable this via Service Management REST APIs for Create and Update Storage Account or via the Windows Azure Portal. Current options for geo replicating data in your storage account are GRS (Geographically Redundant Storage) and RA-GRS (Read-Access Geographically Redundant Storage). For more information on this, please refer to blog post here.
I guess you mean Ge-Replication for a Storage Account. You should be able to enable it from the management portal.
You can optionally enable read from secondary, which will give you read access to the data on the secondary.
We are implementing a service/message-bus feature in our SignalR application and have been looking at Redis, with automatic fail-over using Redis Sentiel. We would like to maintain our own servers and have read SignalR powered by Service Bus. Since this is a Winddows Azure implementation, how can I accomplish this in our internal network with VM's with automatic fail-over similar to the Redis solution discussed above?
You may want to look at Service Bus for Windows Server:
http://msdn.microsoft.com/en-us/library/windowsazure/jj193022(v=azure.10).aspx
It has API symmetry between Azure Service Bus and the Windows Server API (particularly for messaging: queues and topics/similar to SignalR). It doesn't include the caching and ACS services. However, if you want the Azure Service Bus - Caching...you can get that in:
AppFabric for Windows Server
http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx