Infrastructure

Infrastructure

275 bookmarks
Custom sorting
Why I Won't Use Next.js
Why I Won't Use Next.js
From the perspective of web standards to concerns about increasing complexity, Kent C. Dodds shares his opinions on why he won't use Next.js.
·epicweb.dev·
Why I Won't Use Next.js
Why I'm Using Next.js
Why I'm Using Next.js
Responding to an article sharing feedback about Next.js with my opinions.
·leerob.io·
Why I'm Using Next.js
X celebrates 60% savings from cloud exit
X celebrates 60% savings from cloud exit
Musk has taken a cleaver to the costs and complexity at X. It hasn't always been pretty, but it sure has been effective, and in the process, he's proven his detractors wrong time and again. Not only has the site stayed up, despite hysteric proclamations that it would crater soon after his personnel changes, but X has been able to incre...
·world.hey.com·
X celebrates 60% savings from cloud exit
Microservices aren't the problem. Incompetent people are
Microservices aren't the problem. Incompetent people are
There's been a lot of (deserved) criticism towards microservice architecture and how it's usually hurtful to the companies. However, I believe SOA isn't bad ...
·nondv.wtf·
Microservices aren't the problem. Incompetent people are
Lessons Learned by a Software Guy Venturing into Hardware
Lessons Learned by a Software Guy Venturing into Hardware
I've been in the software game for almost 30 years professionally, with another 10 dabbling in programming. I'm one of those who think anyone can code, but creating a software product...
·sidecart.xyz·
Lessons Learned by a Software Guy Venturing into Hardware
10 insights on real world container use | Datadog
10 insights on real world container use | Datadog
Our latest report examines more than 2.4 billion containers run by tens of thousands of Datadog customers to understand the state of the container ecosystem.
·datadoghq.com·
10 insights on real world container use | Datadog
New for Amazon SQS – Update the AWS SDK to reduce latency | Amazon Web Services
New for Amazon SQS – Update the AWS SDK to reduce latency | Amazon Web Services
With Amazon SQS, you can send and receive messages between software components at any scale. It was one of the first AWS services I used and as a Solutions Architect, I helped many customers take advantage of asynchronous communications using message queues. In fact, Amazon SQS has been generally available since July 2006 and, under […]
·aws.amazon.com·
New for Amazon SQS – Update the AWS SDK to reduce latency | Amazon Web Services
EP83: Explaining 9 Types of API Testing
EP83: Explaining 9 Types of API Testing
This week’s system design interview: Python Vs C++ Vs Java! (Youtube video) Explaining 9 types of API testing API Vs SDK! System Design for Everyone! Explain the Top 6 Use Cases of Object Stores How to Build Your Engineering Metrics Program (Guide) (Sponsored)
·blog.bytebytego.com·
EP83: Explaining 9 Types of API Testing
The State of Micro Frontends - Bits and Pieces
The State of Micro Frontends - Bits and Pieces
One of the more controversial topics in frontend web dev is microfrontends. Are they worth it? Should you really split up your application?
·blog.bitsrc.io·
The State of Micro Frontends - Bits and Pieces
Serverlesspresso
Serverlesspresso
Serverlesspresso workshop
·workshop.serverlesscoffee.com·
Serverlesspresso
Introducing the Next Generation of AWS Amplify’s Fullstack Development Experience | Amazon Web Services
Introducing the Next Generation of AWS Amplify’s Fullstack Development Experience | Amazon Web Services
AWS Amplify just announced a public preview of a new code-first developer experience that empowers frontend developers to quickly build and deploy fullstack apps with their existing TypeScript or Javascript skills. The first generation of the tooling offered a tooling-first experience, using a CLI/Console-based interactive workflow to create a backend. Gen 2 transitions to a […]
·aws.amazon.com·
Introducing the Next Generation of AWS Amplify’s Fullstack Development Experience | Amazon Web Services
Scaling Kubernetes to 7,500 nodes
Scaling Kubernetes to 7,500 nodes
We’ve scaled Kubernetes clusters to 7,500 nodes, producing a scalable infrastructure for large models like GPT-3, CLIP, and DALL·E, but also for rapid small-scale iterative research such as Scaling Laws for Neural Language Models.
·openai.com·
Scaling Kubernetes to 7,500 nodes
Sharding Pinterest: How we scaled our MySQL fleet
Sharding Pinterest: How we scaled our MySQL fleet
This is a technical dive into how we split our data across many MySQL servers. We finished launching this sharding approach in early 2012, and it’s still the system we use today to store our core…
·medium.com·
Sharding Pinterest: How we scaled our MySQL fleet
Sharding & IDs at Instagram
Sharding & IDs at Instagram
With more than 25 photos and 90 likes every second, we store a lot of data here at Instagram. To make sure all of our important data fits…
·instagram-engineering.com·
Sharding & IDs at Instagram