Posts Tagged 'Visualization'

May 10, 2012

The SoftLayer API and its 'Star Wars' Sibling

When I present about the SoftLayer API at conferences and meetups, I often use an image that shows how many of the different services in the API are interrelated and connected. As I started building the visual piece of my presentation, I noticed a curious "coincidence" about the layout of the visualization:

SoftLayer API Visualization

What does that look like to you?

You might need to squint your eyes and tilt your head or "look beyond the image" like it's one of those "Magic Eye" pictures, but if you're a geek like me, you can't help but notice a striking resemblance to one of the most iconic images from Star Wars:

SoftLayer API == Death Star?

The SoftLayer API looks like the Death Star.

The similarity is undeniable ... The question is whether that resemblance is coincidental or whether it tells us we can extrapolate some kind of fuller meaning as in light of the visible similarities. I can hear KHazzy now ... "Phil, While that's worth a chuckle and all, there is no way you can actually draw a relevant parallel between the SoftLayer API and The Death Star." While Alderaan may be far too remote for an effective demonstration, this task is no match for the power of the Phil-side.

Challenge Accepted.

The Death Star: A large space station constructed by the Galactic Empire equipped with a super-laser capable of destroying an entire planet.

The SoftLayer API: A robust set of services and methods which provide programmatic access to all portions of the SoftLayer Platform capable of automating any task: administrative, configuration or otherwise.

Each is the incredible result of innovation and design. The construction of the Death Star and creation of the SoftLayer API took years of hard work and a significant investment. Both are massive in scale, and they're both effective and ruthless when completing their objectives.

The most important distinction: The Death Star was made to destroy while the SoftLayer API was made to create ... The Death Star was designed to subjugate a resistance force and destroy anything in the empire's way. The SoftLayer API was designed to help customers create a unified, automated way of managing infrastructure; though in the process, admittedly that "creation" often involves subjugating redundant, compulsory tasks.

The Death Star and the SoftLayer API can both seem pretty daunting. It can be hard to find exactly what you need to solve all of your problems ... Whether that be an exhaust port or your first API call. Fear not, for I will be with you during your journey, and unlike Obi-Wan Kenobi, I'm not your only hope. There is no need for rebel spies to acquire the schematics for the API ... We publish them openly at, and we encourage our customers to break the API down into the pieces of functionality they need.

-Phil (@SoftLayerDevs)

June 23, 2011

IPv6 - Blocks, Slashes and Big Numbers

IPv4 addresses are 32-bit while IPv6 addresses are 128-bit. Customers can get a /64 allocation of IPv6 addresses provisioned to a single SoftLayer server. A /64 block of IPv6 addresses contains 18,446,744,073,709,551,616 distinct addresses. The entire IPv4 address space is 4,294,967,296 distinct addresses.

It's easy to get lost in a sea of numbers when you start talking about IPv4 and IPv6 address space. With the exhaustion of IPv4 address space and the big push toward IPv6, everyone's talking about address blocks, usage justification and dual stack compatibility, but all of those conversations presuppose a certain understanding of why IP addresses are the way they are. Someone can say, "The IPv6 pool is exponentially larger than the IPv4 pool," but that statement needs a little context when you hear that providers like SoftLayer are provisioning a free /64 IPv6 allocation of 18,446,744,073,709,551,616 addresses to a single server. If the entire IPv4 pool on the Internet is 4,294,967,296 addresses and we're giving away that many IPv6 addresses to a single server, a simple question logically follows:


Are the Internet authorities being irresponsible when they're allowing such huge numbers of IPv6 addresses to be assigned to individual servers without a demonstrated need for that many addresses? Will this "wastefulness" lead to another IP address pool depletion in our lifetime? These questions are completely legitimate, and they're much easier to explain in a visualized format than they are if we answered them line-by-line in text:

The video duration might seem intimidating, especially if you consider that all 15 minutes are spent talking about IP addresses (Woohoo!), but there's a lot of information, and we did our best to break it down to simple pieces that logically follow each other to help you get the full picture of the world of IP addresses. We explain what CIDR Slash (/) Notation (where you see IP address blocks written as ""), and we offer a simple trick to calculate the number of distinct addresses available in a given IPv4 block. There's a fair amount of witty (and not-witty) banter and at least one use of the word "ridonkulous," so if you enjoyed the DC Construction video commentary, you'll get a kick out of this one too.

Toward the end of the video, we speak directly to why SoftLayer is able to give a /64 of IPv6 addresses to every server and what that means for the future of the IPv6 space.

Fun Fact: SoftLayer IP Address Space*

  • IPv4: 872,448 Addresses
  • IPv6 (/32): 79,228,162,514,264,337,593,543,950,336 Addresses

*Does not include IP space assigned to The Planet

Did the video help you wrap your mind around the differences between IPv4 and IPv6? Do you have any more questions about the differences between the two or how SoftLayer is approaching them?


Subscribe to visualization