IAAS, CLOUD, AND MANAGED SERVICES BLOG
Many of the people reading these words are at work. They are looking at a screen connected to a computer that contains gigabytes of data and applications crucial to their productivity. Without the device, they are unable to work. Almost everyone else reading this article will have a smartphone in hand. Smartphones like the iPhone can carry gigabytes of data, but almost all of it will also live in the cloud and be accessible from any other device.
With the restructuring of our IaaS cloud server platform, we offer even better value for money with a tiered structure that empowers enterprise cloud clients to choose the best resource profile for their workloads. We've been hosting enterprise clients for a decade and half. Over the years we've developed a deep insight into the infrastructure hosting needs of business. To further empower our clients to deploy — and pay for — exactly the infrastructure they need, we've restructured our infrastructure-as-a-service offering.
Cartika is pleased to introduce New Relic analytics integration and roll out (phased roll out outlined below). We are very excited about this roll out and what it will mean for both our customers, and internally for our support staff to have access to this data. The benefits it will present to our customers is simply enormous. Developers, Sys Admins and DBA's will gain invaluable insights into the health of their environments, be able to more quickly identify problems, streamline their resource usage and make educated decisions about capacity and capacity planning. Internally, we are very excited to provide these sorts of tools and analytics to our support staff. Their ability to help customers identify issues, identify bad plugins or bad code and provide advise and consultations regarding upgrading strategies, code optimization and various other day to day issues is simply increased exponentially and dramatically. Their ability to identify such issues is expedited by presenting them the data in real time, in an easy to understand and clearly defined interface. We are enabling our support staff, with the tools they need, to quickly and efficiently provide the superior level of service and support we demand from our team.
A troubling report was published earlier this month by IT consulting firm Antithesis Group. Through a partnership with Stanford University and TSO Logic, the firm examined the state of data centers all across the world. Among its findings was the revelation that at least 30% of data center servers have been idle in excess of six months. They are, as the study puts it, ‘comatose.’ And there are at least ten million of them.
Lets say you have very popular website. It’s been chugging along fine for the last couple of months; your server has handled the load perfectly well. But as your site becomes ever more popular, the server starts to show the strain — too many connections swamp the available memory, pages load slowly, and sometimes not at all. It’s time for an upgrade.
If you've been in the IT industry for a while, you'll have an almost instinctive familiarity with what the cloud is, its various modalities, deployment models, and types. Intuitively, one would think that a deep understanding would make the cloud easy to explain to less technical people, but in fact the opposite is true. It's very difficult to put yourself in the mindset of someone who lacks the conceptual framework that those of us who have been around enterprise IT for a long time have developed.
There has always been a lot of confusion around the exact meanings of the various cloud service models and their intersection with deployment strategies. That's hardly surprising given that IaaS, PaaS, SaaS, public cloud, private cloud, hybrid cloud, and a dozen other as-a-service modalities are a complex combination of marketing speak and technical jargon. In this article, I'd like to tease out one confused strand: the relationship between Infrastructure-as-a-Service and public or private cloud deployments. I've chosen to address this topic because there's often considerable confusion around what a private cloud is: I've heard people say that a private cloud can't involve virtualization, that its just another name for traditional in-house deployments, that it's a form of colocation, that Google Apps is a private cloud, and so on — none of which are remotely accurate or at least not completely so.
Even the smallest of modern companies use networks that are both heterogeneous and dispersed. Business networks are composed of multiple services spread over many servers in diverse locations. I'm a writer, so you'd think I could make do without much of a network, but when I add up all the services I use to run my small business, I find that I rely on an extensive network of personal computers, mobile devices, backup servers, file servers, cloud storage servers, virtual private servers, SaaS applications, web hosting servers, and email services; hosted in the cloud, in my home, and on traditional hosting; and distributed all over Europe and the US.
If there’s one thing that’s obvious to anyone who’s spent even a little bit of time online, it’s that security is one of the biggest hot-button issues on the modern web. As we store more and more information online, cyber-attacks are becoming increasingly lucrative - and the stakes involved in securing our data are rising ever higher. Not surprisingly, that means cyber-criminals are getting smarter and craftier. Whereas before a business might have to deal with the odd DDOS or man-in-the-middle attack, now there’s a constant risk that someone might jump in to exploit even the smallest security hole. It’s a culture of not-completely-unjustified paranoia - particularly since it seems as though many organizations aren’t pulling their weight as far as protecting their data is concerned.
Much of the thinking around data storage and processing construes enterprise data as an undifferentiated mass. The reality is very different. Data is differentiated across multiple axes: from low to high value, from business critical to potentially useful, from highly sensitive to publishable, and from time sensitive to archival, among many other potential lines of variation. No one-size-fits-all solution can be sufficient to accommodate the matrix of potential species of data and their meaning to a particular enterprise.