Join the Cisco DemoFriday on September 25th and learn how you can benefit from network programmability as you transition from legacy systems to open standard interfaces.
This is a guest post by Yiftach Shoolman, Co-founder & CTO of redislabs. Will 3D XPoint change everything? Not as much as you might hope...
Recently, investors, analysts, partners and customers have asked me how the announcement from Intel and Micron about their new 3D XPoint memory technology will affect the in-memory databases market. In these discussions, a common question was “Who needs an in-memory database if all the non in-memory databases will achieve similar performance with 3D XPoint technology?” Well, I think that's a valid question so I've decided to take a moment to describe how we think this technology will influence our market.
First, a little background...
The motivation of Intel and Micron is clear -- DRAM is expensive and hasn’t changed much during the last few years (as shown below). In addition, there are currently only three major makers of DRAM on the planet (Samsung Electronics, Micron and SK Hynix), which means that the competition between them is not as cutthroat as it used to be between four and five major manufacturers several years ago.
A five-year-old upstart garners investments from Google, Microsoft, Baidu, and Qualcomm and sets its sights on competing with Amazon Web Services.
Datiphy watches how data is being used — a managed service that's being turned into a software product for the U.S. market.
Ethan has an excellent post up on Interoperate or Die. Herewith, a few thoughts in response.
From my perspective, the importance of open standards in the world of network engineering can hardly be overstated. As networks become more complicated (or complex, depending on what word you want to use), having consistent interfaces will become increasingly important. Think of the old IP model — every transport runs on top of IP, and IP runs on top of every physical/link layer. Using IP as a “choke point” built a “wasp waist,” a single API everyone on both sides of the narrow point in the protocol layer could talk to.
in recent years, we’ve forgotten the wasp waist. We’ve built everything over HTTP, and everything over Ethernet over IP, and everything over GRE over IP, and… The entire stack, above IP, is a hornet’s nest of convoluted caverns and side halls pointing, apparently, everywhere at once (like the guy from the forest in The Point, above).
If you think of IP as an API (which is really what it is), the point is to have a single layer API between any two interacting systems. This creates a clean interaction surface that helps you to Continue reading
When I wrote my stretched VSAN post, I thought VSAN uses asynchronous replication across WAN. Duncan Epping quickly pointed out that it uses synchronous replication, and I fixed the blog post.
The “What about latency?” question immediately arose somewhere in my subconscious, but before I could add that thought to the blog post (because travel), Anders Henke wrote a lengthy comment that totally captured what I was thinking, so I’m including it in its entirety:
Read more ...I recently came across IPython while reading some Python development blogs. IPython is an alternative to the standard Python shell that offers some additional features. When I first read about IPython, I was a little confused because many people refer to it as the ‘Python interactive shell’. While IPython is an interactive shell, it is not the Python interactive shell. For instance, we can enter the Python interactive shell just by typing ‘python’ on our Python development box…
So, what we really did here was invoke the Python interpreter in interactive mode. In this mode, commands can be read from the TTY and directly interpreted. So for example, we can do something like this…
The Python code we type is directly interpreted and we get the output we would expect. So instead of using the Python interpreter to run a .py script, we could do it all directly from the interpreter. So the example from our Python up and running post works just as well in interactive mode as it did when run as a script…
So that’s Python interactive mode. Now, let’s talk about IPython. The first thing we Continue reading
On September 16 2015 at 10:00AM PST, Apple released their latest update to the iPhone: iOS 9. For several days after the announcement, ISPs and customers reported problems downloading iOS 9 due to overloaded servers. Obviously, the demand for iOS 9 was higher than even Apple anticipated, but how much higher? Few organizations outside of Apple have any idea what the actual iOS 9 adoption rates look like.
By analyzing the user agent strings of requests passing through the CloudFlare network, we were able to piece together a pretty good picture of iOS 9 uptake. Here’s an hour-by-hour look at requests from iOS 8 devices (blue) and iOS 9 devices (orange) for the first 24 hours after the announcement.
We started seeing small amounts of iOS 9 usage before it was officially released, followed by a spike immediately after the launch (times are shown in UTC, so the 10:00AM announcement shows up as hour 18). You can also see a second spike at 10:00 UTC when Europe started waking up.
Even though the official release was for iOS 9.0, we also found beta iOS 9.1 in the wild. Curious about the comparative traffic Continue reading
A10 and Blue Coat could find an edge by doing SSL well, one analyst believes.
No, I’m not starting a naming war. Not really. I don’t care if you use ! or # or >> or {} to mark your interface descriptions. I don’t care if you use all-caps or lowercase, or if you feel … Continue reading
The post Interface descriptions – your last hope appeared first on The Network Sherpa.
SK Telecom applies NFV to VoLTE, after dabbling with a vEPC.
