Solr spins up nicely and works effectively for small enterprise environments providing helpful mechanisms for fuzzy searches and facetted searching. For larger enterprises with complex business solutions you'll find the need to hire an expert Solr engineer to optimize the powerful platform to your needs. Internationalization is tricky with Solr and many hosting solutions may limit you to a latin character set.
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.
Easy to get started with Apache Solr. Whether it is tackling a setup issue or trying to learn some of the more advanced features, there are plenty of resources to help you out and get you going.
Performance. Apache Solr allows for a lot of custom tuning (if needed) and provides great out of the box performance for searching on large data sets.
Maintenance. After setting up Solr in a production environment there are plenty of tools provided to help you maintain and update your application. Apache Solr comes with great fault tolerance built in and has proven to be very reliable.
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
These examples are due to the way we use Apache Solr. I think we have had the same problems with other NoSQL databases (but perhaps not the same solution). High data volumes of data and a lot of users were the causes.
We have lot of classifications and lot of data for each classification. This gave us several problems:
First: We couldn't keep all our data in Solr. Then we have all data in our MySQL DB and searching data in Solr. So we need to be sure to update and match the 2 databases in the same time.
Second: We needed several load balanced Solr databases.
Third: We needed to update all the databases and keep old data status.
If I don't speak about problems due to our lack of experience, the main Solr problem came from frequency of updates vs validation of several database. We encountered several locks due to this (our ops team didn't want to use real clustering, so all DB weren't updated). Problem messages were not always clear and we several days to understand the problems.
It takes some time to deploy and currectly maintein it. And also, to learn how to use and integrate in the enviroment as well. Once you get theses steps done, it usability is very simple, and almost of the time it don't require no further attention on it. Even for maintence, if you deploy it on a cluster mode, it is very reliable and easy to take one host down.
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
We tried to use both Elasticsearch and Swiftype with Drupal 8 but there are currently no good modules that integrate Drupal with those solutions. So Solr was really the only option for a Drupal 8 web site. It's not as easy to learn or use as Swiftype, but in the end I think it will be a little less expensive and offer more customization and flexibility.
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
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
