Over a million developers have joined DZone.

How to solve your corporate Dropbox dilemma

DZone's Guide to

How to solve your corporate Dropbox dilemma

· Cloud Zone ·
Free Resource

Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.

For most of us, sharing digital files used to be tricky and time consuming, but since file sharing technology has become commoditised that’s no longer the case. Consumer vendors like Dropbox, Google and Apple have solved what used to be a complexed problem and have turned it into something quite simple, and importantly something that everyone can do at home and at work.

The catch is that these tools are not always great for enterprises. Consumer tools are popular because they’re easy to use and they solve the file sharing problem so well that people have become used to using them on a daily basis. Consequently, workers can get frustrated if their IT departments aren’t providing these kind of applications to them as part of their working tools, and often start using consumer tools to share work content.

This isn’t ideal as this content often includes sensitive information and even client data shared in an insecure environment, and IT can’t keep track of who is sharing what and with whom. Consumer tools themselves are great because they solve the basic file sharing problem, but organisations need to make sure they use tools that are right for the enterprise. Expectations have been set at a very high level by these consumer tools, so IT departments who are trying to meet these requirements need to provide the same consumer-grade user experience.

I ran a webinar where I spoke about the challenges that organisations face when tackling this issue, and explained what IT departments can do to solve the corporate Dropbox dilemma. You can watch my webinar online now.

Join us in exploring application and infrastructure changes required for running scalable, observable, and portable apps on Kubernetes.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}