Enrico Signoretti of Juku writes:
Data grows (steadily… and exponentially) and nothing gets thrown away. Since data adds up, the concept of the “data lake” has taken shape. Even systems created for big data are starting to sense this problem and system architects are beginning to think differently about storage.
I’m going to take Hadoop as an example because this gives a good idea of a hyper converged infrastructure, doesn’t it?
Today, most Hadoop clusters are built on top of a HDFS (Hadoop Distributed File system). HDFS characteristics make this FS much cheaper, reliable and scalable than many other solutions but, at the same time it’s limited by the cluster design itself.
A great look at the types of convergence (or lack thereof) in the market. Hyperconvergence isn’t for everyone. Read on to find out what may work best for you.
- Revealing Security Threats with ExtraHop Reveal(x) - February 13, 2018
- The Logic Of Tables with Broadcom SDKLT - February 8, 2018
- Getting Ready for GDPR - January 18, 2018
- Going Faster with 400Gbps Ethernet and Andy Bechtolsheim - January 12, 2018
- Architecting Container Direction with Nirmata - January 5, 2018
- Continuing the SD-WAN Discussion At FutureWAN - January 4, 2018
- Keeping An Eye On Containers with Ixia CloudLens - January 4, 2018
- Balancing The Cost Of Your Application Delivery Controllers with KEMP Metered Licensing - December 27, 2017
- Arista vs. Cisco – The Tale Up To Now - December 14, 2017
- Unmasking Bad Actors with Gigamon - December 7, 2017