Stuff The Internet Says On Scalability For April 19th, 2019

Wake up! It's HighScalability time:

 

Spirit? Smoke? Lightning? Nope. It's a gorgeous LIDAR image showing 1500 years of Willamette River movement (@Blacky_Himself)

 

Do you like this sort of Stuff? I'd greatly appreciate your support on Patreon. I wrote Explain the Cloud Like I'm 10 for people who need to understand the cloud. And who doesn't these days? On Amazon it has 44 mostly 5 star reviews (102 on Goodreads). They'll learn a lot and hold you in awe.

 

  • 536: IRS tax return submissions per second; 400,000: drone planted trees in a day; 200 million: smart speaker observers installed by year end; 54 million: GoT pirated in first 24 hours; 123,052: kg of crashed human spacecraft on the surface of the moon; 610 pounds: 128 kilobytes of  IBM S/360 core memory; 33%: per account month over month Lambda function growth; $100,000: Netflix bug bounty payout; $1 million: Shopify bug bount payout; ~$2300: cost to transfer 23TB from S3 to Backblaze B2 in 7 hours; 14%: Netflix users share passwords; 88%: believe P != NP; 30-90: minutes saved by StackOverflow per week; 83%: US teens have Continue reading

Heavy Networking 443: Architects Vs. Engineers – What’s The Difference?

What's the difference between network architects and network engineers? On today's Heavy Networking we gather four people who've held both roles to explore this question. Topics include the career path to becoming an architect, the tradeoffs, and advice for those pursuing such a role.

The post Heavy Networking 443: Architects Vs. Engineers – What’s The Difference? appeared first on Packet Pushers.

A World Without the IGF

Last week in Geneva, the Internet Governance Forum (IGF) Multistakeholder Advisory Group (MAG) met to discuss preparations for IGF Berlin. The Internet Society is concerned that the IGF community is showing signs of fatigue and believes that certain things must be improved in order for it to survive in an increasingly crowded Internet policy arena. We also believe the world is much better with the IGF than without it.

As the IGF reaches its fourteenth year, we must ask ourselves if it is still capable of dealing with the myriad governance challenges surrounding the Internet and policymakers – and whether the IGF can continue to evolve the Internet way – into an open and distributed global network of networks grounded in voluntary collaboration.

Imagine a world without the IGF. A world where we won’t be able to welcome people from most corners of the earth, from multiple stakeholder groups, and from diverse viewpoints and perspectives to adress the Internet’s pressing public policy issues. All sharing a common goal, albeit sometimes speaking different languages.

Certain things have indeed improved. We have seen better advanced planning from UNDESA and the IGF Secretariat, along with a supportive, well-organized, and solid support from the Continue reading

Intel follows AMD’s lead (again) into single-socket Xeon servers

I’m really starting to wonder who the leader in x86 really is these days because it seems Intel is borrowing another page out of AMD’s playbook.Intel launched a whole lot of new Xeon Scalable processors earlier this month, but they neglected to mention a unique line: the U series of single-socket processors. The folks over at Serve The Home sniffed it out first, and Intel has confirmed the existence of the line, just that they “didn’t broadly promote them.”[ Read also: Intel makes a play for high-speed fiber networking for data centers ] To backtrack a bit, AMD made a major push for single-socket servers when it launched the Epyc line of server chips. Epyc comes with up to 32 cores and multithreading, and Intel (and Dell) argued that one 32-core/64-thread processor was enough to handle many loads and a lot cheaper than a two-socket system.To read this article in full, please click here

Eating Dogfood at Scale: How We Build Serverless Apps with Workers

Eating Dogfood at Scale: How We Build Serverless Apps with Workers
Eating Dogfood at Scale: How We Build Serverless Apps with Workers

You’ve had a chance to build a Cloudflare Worker. You’ve tried KV Storage and have a great use case for your Worker. You’ve even demonstrated the usefulness to your product or organization. Now you need to go from writing a single file in the Cloudflare Dashboard UI Editor to source controlled code with multiple environments deployed using your favorite CI tool.

Fortunately, we have a powerful and flexible API for managing your workers. You can customize your deployment to your heart’s content. Our blog has already featured many things made possible by that API:

These tools make deployments easier to configure, but it still takes time to manage. The Serverless Framework Cloudflare Workers plugin removes that deployment overhead so you can spend more time working on your application and less on your deployment.

Focus on your application

Here at Cloudflare, we’ve been working to rebuild our Access product to run entirely on Workers. The move will allow Access to take advantage of the resiliency, performance, and flexibility of Workers. We’ll publish a more detailed post about that migration once complete, but the experience required that we retool some of our Continue reading

Technology Short Take 112

Welcome to Technology Short Take #112! It’s been quite a while since the last one, as life and work have been keeping me busy. I have, however, finally managed to pull together this list of links and articles from around the Internet, and I hope that something I’ve included here proves useful to readers.

Networking

Servers/Hardware

Nothing this time around! I’ll stay alert for content I can include next time.

Security

Using Faucet to Build SC18 Network with OpenFlow

Remember how Nick Buraglio tried to use OpenDaylight to build a small part of SuperComputing conference network… and ended up with a programmable patch panel?

This time he repeated the experiment using Faucet SDN Controller – an OpenFlow controller focused on getting the job done – and described his experience in Episode 101 of Software Gone Wild.

We started with the usual “what problem were you trying to solve” and quickly started teasing apart the architecture and got geekily focused on interesting things like:

Read more ...