Virtually everyone with a pulse on technology has heard the hype about “moving to the cloud”. Most people just assume that it’s the obvious thing to do in a world where they are virtually always online. I jumped on the bandwagon myself recently, checking out the latest version of Microsoft Office in the cloud, known … Read more
Our Network Solutions and Services Team (NSS) provides premium I.T. consulting services with a focus on complex design, implementation, performance and optimization of our clients’ networks. Our engineers directly contribute to our clients’ success, deploying the latest networking technologies in the highly dynamic environments where they operate. NSS Engineers possess hands-on experience with a variety … Read more
In a recent report, research organization Gartner predicted that 70% of professionals will conduct their work on personal smart devices by 2018. To translate- Gartner effectively predicted that 70% of employees will be working on their own smartphones or tablets by 2018, a concept generally referred to as BYOD, or Bring Your Own Device.
If BYOD plays out as Gartner predicts than this will be a huge change in the workplace, and one that requires some extensive planning to implement properly, with minimal friction.
As previously stated, enterprise-class organizations are jumping onto the private cloud at much higher rates than the public cloud. Why are they doing this, and will this choice of private-over-public really spell the doom of a whole generation of Chief Information Officers, as some public-cloud boosters argue?
Public vs Private: Defined
The public cloud is the cloud we’ve all heard about, a space of shared storage, of software-as-service, a place where your organization doesn’t have to own any hardware of its own. In fact, the public cloud is sold as a place where your organization doesn’t need to hold any software of its own either, or really much of anything other than a few shipments of smartphones and tablets.
By contrast, the private cloud is a remote-hosted network solution that offers just about all of the streamlined benefits of the public cloud, but with a lot more control and security. In the public cloud the infrastructure hosting your network is shared with a bunch of other organizations. In fact, the infrastructure is shared with as many other organizations as your service provider thinks they can cram on theirs. By contrast, in the private cloud your organization’s data and applications are stored and managed through infrastructure that’s used exclusively by your own organization.
When you hear about virtualized business environments, remote-hosted network solutions and IP telephony services, you might think that all of these terms represent a single monolithic technology. While it’s clear the qualities of these services vary from vendor to vendor, not everyone is aware of the fact there are plenty of different deployment methods for each of these. In fact, the differences between one remote-hosted network deployment and another can be rather dramatic.
One of the biggest divides in the world remote-hosted networks lies between private and public cloud deployment. And while public clouds may be getting all the press, private clouds appear to be the deployment method the enterprise market is jumping to.
The truth is – any system is only as reliable as its weakest component. Here are some tips on making a reliable VoIP system:
Most people see the benefits associated with IP telephony and feel pretty sold on the technology right off the bat. This isn’t too surprising. After all, it’s pretty natural to hear benefits like “lowered overhead,” “increasing organizational flexibility,” “expanded feature sets,” and to automatically say yes to whatever technology hands them over. But there are some people who feel a little skittish about IP telephony and aren’t completely wooed by the technology’s many benefits. Instead, these people let their concerns over the technology’s performance overwhelm their decision making process and they end up hemming-and-hawing instead of taking the plunge into IP telephony.
Thankfully many of the concerns some organizations feel over adopting IP telephony are unfounded or easy to guard against with proper provisioning. For example, let’s take a minute to look over a common concern related to IP telephony reliability, to see how well it stands up in the light of day.
As a service provider offering essential phone service to our clients we need to make a lot of tough decisions regarding how we run our business, and that’s doubly true when our clients experience rough economic times. This is true not only for DLS but for many other smaller companies that develop close, personal relationships with their business clients over the years.
On the one hand service providers can be rather hard-nosed and impersonal with their clients and demand full payment, on time, every time their bill comes up due. Lots of providers take this approach. They don’t listen when their clients experience financial difficulties and they don’t make any overtures to help their partners out when times get tough. This hard-nosed approach is pretty common among larger service providers who tend to be less likely to ever meet their clients half-way.
There’s one more point deserving a quick mention in the discussion over Yahoo!’s decision to ban work from home arrangements and how this might impact the way other businesses approach the whole topic within their own organizations.
The CEO Question
A lot of the debate over whether or not Yahoo! did the right thing banning work-from-home arrangements has read as a debate over whether or not Yahoo!’s CEO, Marissa Mayer, made the right decision implementing this ban.
While it’s probably not fair to place the full weight of this decision on Mayer alone, it’s wise to note when these sorts of shake-ups occur they’re usually discussed entirely as the sole decision of whomever is in charge, in this case the company’s CEO.