The only reason I didn't gave the maximum rating is because it's not cheap, if you have a smaller company you can use some plugins instead depending on what you need. But I completely understand it's not safer than the Island browser. However, it would be great to have a simpler version for small companies too, that wouldn't require much testing to setup. Besides that, Island is my first choice when thinking about safety for remote workers.
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
The agent can still see the customer's data that they need to help the customers, but without the ability to screenshot, copy and download outside the Island browser, that also prevent data leaks
The organization also saves money without the need of hiring only local employees, people can download it on their personal desktops
Can replace setups with VPN that are expensive or virtual desktops
Blocks unsafe websites that can also copy the client and customer data
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
It requires some training but it's very easy to use, as it's much like other famous browsers and it behave just as them. Even if it needs to be set up, you can set different policies for different users, that can be quite useful for bigger companies. However, some employees can feel a bit restricted as it has it's limitations to download or copy and paste
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Chrome Remote Desktop is a good option to access the company desktop remotely, but it doesn't reduce the costs of the company since you'll still need to have two machines for it to work, you'll also need the same amount of IT staff and mantain a physical address. It can be a good option to companies that have only few agents remote but it's not good for hybrid or remote only employees
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
There is some costs to training people to use Island, and also to test and setup the browser, if you're initiating a business, this should be considered
Some advisors may not have a compatible hardware, this can add to the migration costs
No need to have a physical address or servers, since everything is managed from the clould it can significantly lower the costs
You can reduce the IT staff and maintenance costs too
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
