Linux Foundation backs a group to boost edge networking

The Linux Foundation announced the foundation of a new umbrella group called LF Edge designed to help unify a fragmented edge-computing marketplace and offer a common framework for future edge projects.The initial announcement lists five open source projects that will serve as the nucleus of the LF Edge framework. Those projects are: EdgeX Foundry – Originated at Dell/EMC, EdgeX Foundry is a platform-agnostic software framework that allows for plug-and-play integration of microservices and is designed to run on any industrial edge gateway, creating a bridge layer between sensors and the cloud. Home Edge Project – Contributed by Samsung, the Home Edge Project looks like an attempt to do for consumer IoT what EdgeX Foundry is doing for industrial IoT – a run-anywhere services layer for home-based IoT devices. Akraino Edge Stack – Taking up the cloud end of the stack is Akraino Edge Stack, which is designed to automate provisioning and offer flexibility and scalability at the back end to businesses trying to run edge services with a cloud back end. The original code was contributed by AT&T. Project EVE – A contribution of IoT software maker Zededa, Project EVE is so named because it’s an edge-virtualization engine. The Continue reading

More on Leaky Abstractions

When I was writing the Back to Basics blog post I reread the Law of Leaky Abstractions masterpiece. You’ll love it – the first example Joel uses is TCP.

However, what really caught my eye was this bit:

The law of leaky abstractions means that whenever somebody comes up with a wizzy new code-generation tool that is supposed to make us all ever-so-efficient, you hear a lot of people saying “learn how to do it manually first, then use the wizzy tool to save time.”

You should apply the same wisdom to shiny new gizmos launched by network virtualization vendors… oh wait, you can’t, they are mostly undocumented black boxes. Good luck ;)

Sadly, the Law of Leaky Abstractions blog post was written in 2002… and nothing changed in the meantime, at least not for the better.

Programming paradigms for dummies: what every programmer should know

Programming paradigms for dummies: what every programmer should know Peter Van Roy, 2009

We’ll get back to CIDR’19 next week, but chasing the thread starting with the Data Continuum paper led me to this book chapter by Peter Van Roy mapping out the space of programming language designs. (Thanks to TuringTest for posting a reference to it in a HN thread). It was too good not to take a short detour to cover it! If you like the chapter, you’ll probably enjoy the book, ‘Concepts, Techinques, and Models of Computer Programming’ by Van Roy & Hardi on which much of this chapter was based .

This chapter gives an introduction to all the main programming paradigms, their underlying concepts, and the relationships between them… We give a taxonomy of about 30 useful programming paradigms and how they are related.

Programming paradigms are approaches based on a mathematical theory or particular set of principles, each paradigm supporting a set of concepts. Van Roy is a believer in multi-paradigm languages: solving a programming problem requires choosing the right concepts, and many problems require different sets of concepts for different parts. Moreover, many programs have to solve more than one problem! Continue reading

Getting start with RSVP

We’ve spent a great deal of time in the last few posts talking about MPLS both with LDP and with static LSP configurations. While these approaches certainly work, they aren’t the only options to use for label distribution and LSP creation. If we take static LSPs off the table (since they’re the equivalent of static routes and not scalable) we really have two main choices for label distribution – LDP and RSVP. LDP is typically considered to be the easiest of the two options but also offers a limited set of functionality. RSVP offers many more features but also requires more configuration. When you’re designing an MPLS network you’ll have to decide which protocol to use based on your requirements. In many cases a network may leverage both in different areas. In this post the aim is just to get RSVP up and running – we’ll dig into the specifics in a later post.

So let’s get right into a simple lab where we leverage RSVP instead of LDP. Like the previous post, we’ll leverage the same lab environment…

Let’s assume as before that the base configuration of the lab includes all the routers interfaces configured, OSPF enabled on all Continue reading

Cisco’s AppDynamics software ties in SDN, serverless for greater app management

Cisco’s AppDynamics business rolled out a raft of enterprise technologies it said will help customers better manage everything from software-defined networks and serverless computing environments to application performance.The wide-ranging announcement – easily AppDynamics largest technology upgrade since being acquired by Cisco two years ago – targets enterprise customers looking to monitor performance and automate the response to problems in business applications. [ Learn more about SDN: Find out where SDN is going and learn the difference between SDN and NFV. | Get regularly scheduled insights by signing up for Network World newsletters. ] The rollout included key components such as a Cognition Engine that will be the basis for future automation and artificial intelligence-based application performance management and the integration of AppDynamics application monitoring tools and Cisco’s Application Centric Infrastructure (ACI) technology to help customers mix application health and network operations management in the data center and multi-cloud environments.To read this article in full, please click here

Cisco’s AppDynamics software ties in SDN, serverless for greater app management

Cisco’s AppDynamics business rolled out a raft of enterprise technologies it said will help customers better manage everything from software-defined networks and serverless computing environments to application performance.The wide-ranging announcement – easily AppDynamics largest technology upgrade since being acquired by Cisco two years ago – targets enterprise customers looking to monitor performance and automate the response to problems in business applications. [ Learn more about SDN: Find out where SDN is going and learn the difference between SDN and NFV. | Get regularly scheduled insights by signing up for Network World newsletters. ] The rollout included key components such as a Cognition Engine that will be the basis for future automation and artificial intelligence-based application performance management and the integration of AppDynamics application monitoring tools and Cisco’s Application Centric Infrastructure (ACI) technology to help customers mix application health and network operations management in the data center and multi-cloud environments.To read this article in full, please click here

Cisco’s AppDynamics software ties in SDN, serverless for greater app management

Cisco’s AppDynamics business rolled out a raft of enterprise technologies it says will help customers better manage everything from software-defined networks and serverless computing environments to application performance.The wide-ranging announcement – easily AppDynamics largest technology upgrade since being acquired by Cisco two years ago – targets enterprise customers looking to monitor performance and automate the response to  problems in business applications.  [ Learn more about SDN: Find out where SDN is going and learn the difference between SDN and NFV. | Get regularly scheduled insights by signing up for Network World newsletters. ]To read this article in full, please click here

Cisco’s AppDynamics software ties in SDN, serverless for greater app management

Cisco’s AppDynamics business rolled out a raft of enterprise technologies it says will help customers better manage everything from software-defined networks and serverless computing environments to application performance.The wide-ranging announcement – easily AppDynamics largest technology upgrade since being acquired by Cisco two years ago – targets enterprise customers looking to monitor performance and automate the response to  problems in business applications.  [ Learn more about SDN: Find out where SDN is going and learn the difference between SDN and NFV. | Get regularly scheduled insights by signing up for Network World newsletters. ]To read this article in full, please click here

Stuff The Internet Says On Scalability For January 25th, 2019

Wake up! It's HighScalability time:

 

My god, it's full of synapses! (3D map of a fly's brain)

 

Do you like this sort of Stuff? Please go to Patreon and do what comes natural. Need cloud? Stand under Explain the Cloud Like I'm 10 (35 nearly 5 star reviews).

 

  • 10%: Netflix captured screen time in US; 8.3 million: concurrent Fortnite players;  773 Million: Record "Collection #1" Data Breach; 284M+: Reddit monthly views; 1 billion: people impacted by data breaches; 1st: seed germinated on the moon; 4x: k8s api growth from v1 to v1.4; 7x: faster PyPy python; 9B: gallons of water/day for lawns; 2.6 terabytes: largest data leak in history; $14B: serverless market by 2024; 100 million: Alexas sold; 51%: mobile games share of global market; 160 TB: total data transfer during re:Invent 2018; 100+ million: stackoverflow users; 40%: increase in median data usage; 3%: drop in Comcast's network spending; 1 billion: tweets about gaming in 2018; 53%: investment of Baidu, Alibaba, and Tencent in China's 190 major AI companies; 104,954: hard drives Continue reading

HTTP/3: From root to tip

HTTP/3: From root to tip

HTTP is the application protocol that powers the Web. It began life as the so-called HTTP/0.9 protocol in 1991, and by 1999 had evolved to HTTP/1.1, which was standardised within the IETF (Internet Engineering Task Force). HTTP/1.1 was good enough for a long time but the ever changing needs of the Web called for a better suited protocol, and HTTP/2 emerged in 2015. More recently it was announced that the IETF is intending to deliver a new version - HTTP/3. To some people this is a surprise and has caused a bit of confusion. If you don't track IETF work closely it might seem that HTTP/3 has come out of the blue. However,  we can trace its origins through a lineage of experiments and evolution of Web protocols; specifically the QUIC transport protocol.

If you're not familiar with QUIC, my colleagues have done a great job of tackling different angles. John's blog describes some of the real-world annoyances of today's HTTP, Alessandro's blog tackles the nitty-gritty transport layer details, and Nick's blog covers how to get hands on with some testing. We've collected these and more at https://cloudflare-quic.com. And if that tickles your fancy, be sure Continue reading

1 … 1,380 1,381 1,382 1,383 1,384 … 3,885