Electronic components generate a lot of heat. Keeping them cool can get expensive. Let's discuss some options.
This year Ericsson is attending Amazon re:Invent for the first time. Before I share some of my reflections from the event, I would like to look back for a bit.
As applications and services move into virtualized environments, and network speeds leap from 10Gbps (yesterday) to 25/40Gbps (today) to 100Gbps in coming years, the legacy methods of monitoring application flows don’t scale. At the same time, with overlays and underlays and associated complexity, there is a bigger need to monitor every application and every application flow.
Let's explore the different ways applications store data permanently on disk. The different methods are in some sense merely conveniences for the programmer writing an application.
At its heart, all data storage consists of a stream of zeros and ones on some medium. Paper and magnetic tape have given way to disk, but the principles remain the same. When we talk about storage methods, we mean the structure imposed on these zeros and ones to provide the semantics necessary for storing them—that is, the ability to express ideas such as data ownership, security, access method, and even clues as to what type of data it is that we are storing.
I will begin the discussion with the most familiar method (file storage) and then discuss block storage (the way databases store data for us), and finally I will briefly discuss object-based storage, which is a method modern applications use to move data structures from working memory to disk.
It's time to face up to some truths about cloud from an organizational perspective. Today, many businesses – both vendors and enterprises – are attempting cloud for the second or third time (in some cases, it’s even more). And there’s a growing realization that cloud is much more than a technology or architecture question – it comes down to organization and often just plain old willpower.