box.build: Q&A with Senad Dizdar, CEO of cloudHQ

cloudhqHow was cloudHQ started?

cloudHQ was founded in 2011 and is based in San Francisco, CA. cloudHQ was initially envisioned as a system for users to index all their cloud data with the ability for simple searching – similar to Greplin. Soon after, we found that the demand for cloud search and management was not very high. After talking with our customers, we found that they wanted a solution that would synchronize, backup, consolidate, and integrate their data that they’re already storing in their cloud accounts. As demand for competent data loss solutions grew, cloudHQ expanded to provide this solution to enterprise business.

Why did you choose to focus on the enterprise space? Why is this space interesting to you?

We’ve found that especially in the cloud, the correlation between how much a company values their data and company size increases exponentially over time.

Customers that use their computers for leisure don’t typically place as high a value on their data as companies who are expanding and experiencing growth. Enterprise businesses on the other hand, highly value their consolidation and integration of data exchanges by backing them up in the cloud.

Why did you choose to integrate with Box?

Box has one of today’s best solutions for online backup services to allow for easy file sharing and reliable data access. For example, many of our clients prefer to use Box for security reasons because it’s HIPAA compliant, ensuring them national standards of data security.

What advice would you give to other Box developers?

One advice for developers which are using Box’s API is that when building a product which interacts with third party APIs, it’s very important to spend some time to design, develop and setup a scalable and reliable system for logging, debugging, and measurement of your modules which use Box’s API and for Box API calls itself. For example, each API call should have certain "expected" operational characteristics: latency, transfer speed, etc. So your system should be able to detect any behavior outside "expected" / "normal" characteristics.  By having that, you can then tweak your product to work more efficiently and reliably with Box’s API.

What are some of the newest and most interesting technologies that you are using?

We borrow our mantra from Edsger W. Dijkstra: “Simplicity is a prerequisite for reliability.”

Although we try to always balance the richness of our technology with an intuitive UI, we’re proud to have developed a scalable model on our backend that’s based on our proprietary low-level replication system, specifically designed to store meta-data. This replication system allows for a two-way replication (master-master) between Berkeley embedded databases and two-way replication between MySQL databases as well.

How do you see the world of enterprise focused mobile apps evolving in the future?

Since mobile is quickly becoming the most convenient way to work, it makes sense that data is moving to the cloud. As such, data cloud storage is increasingly more prevalent than in on-premise storage solutions. We foresee a growing need for third-party applications to manage cloud data storage, such as in the following examples:
to simplify the provisioning and onboarding process for newly hired employees or deprovisioning for people who left the company, data security, and sharing/collaboration.

The evolution of enterprise-focused cloud apps will certainly be interesting. Individuals, small businesses, large enterprises, government agencies- we see them all moving to the cloud. Some have been slow to adopt cloud technology, but eventually I believe they will have no choice but to migrate to the cloud in order to keep up with demand and competition.

Tags: sticky