Cloud, Edge & Distributed Systems

AWS/Azure/GCP, serverless, edge, microservices, observability, and SRE.

  • 4 Subtopics
  • 19 Tracked terms
  • Last 30 days Feed window

Inside Cloud, Edge & Distributed Systems

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Cloud, Edge & Distributed Systems


dev.to > technonotes > kubernetes-day-03-file-permissions-bind-mount-336c

Kubernetes - Day - 03 - File Permissions, Bind Mount

31+ min ago   (24+ words) File Permission - chmod 600 <file_name> - chmod -R 6-- <folder_name> -... Tagged with devops, kubernetes, linux....


yahoo.com > news > videos > star-trek-tech-catches-present-001000855.html

Star Trek tech catches up with present day

8+ hour, 26+ min ago   (56+ words) This month marks 60 years since the first episode of Star Trek aired on TV, and Dave Malkoff shows how all these years later, the future is now. This month marks 60 years since the first episode of Star Trek aired on…...


dev.to > uhltak > k3s-statt-kubernetes-warum-die-rancher-distribution-unschlagbar-ist-5d0p

k3s statt Kubernetes: Warum die Rancher-Distribution unschlagbar ist

1+ hour, 20+ min ago   (691+ words) Hier kommt k3s ins Spiel. Entwickelt von SUSE (bzw. Rancher), ist k3s keine abgespeckte Spielzeugversion, sondern eine hochkompakte, aber voll CVE-konforme Kubernetes-Distribution. Sie wurde speziell für IoT, Edge Computing und CI/CD-Pipelines konzipiert, hat sich aber längst auch als extrem robustes Fundament…...


dev.to > miruky > build-a-dynamodb-outbox-and-an-idempotent-sqs-consumer-in-the-console-1e2b

Build a DynamoDB Outbox and an Idempotent SQS Consumer in the Console

1+ hour, 26+ min ago   (1251+ words) Introduction Hi, I'm miruky. A database commit can succeed while the caller believes... Tagged with aws, serverless, dynamodb, tutorial....


engadget.com > 2260477 > wired-vs-wireless-internet-which-choose-for-home

Wired vs. wireless internet: Which should you choose for your home?

1+ hour, 26+ min ago   (706+ words) "Wireless internet" can have two different meanings, so there's an important distinction to make first. This comparison isn't about Wi-Fi versus Ethernet inside your home. Rather, it's about how your internet provider gets the connection to your house. With wired…...


dev.to > israeltheory > automating-deployment-with-github-actions-24i1

Automating Deployment with Github Actions

2+ hour, 34+ min ago   (1511+ words) In the previous article, we learned how to spin up a functioning network and compute resources on AWS, and deploy our application on them. Let's remember a key architectural decision: our EC2 instance is in a private subnet, shielded from the…...


dev.to > stark_zhuang_df5076f35c68 > 1551-elasticsearch-and-1462-memcached-endpoints-two-cache-layers-with-different-defaults-4eo6

1,551 Elasticsearch and 1,462 Memcached Endpoints: Two Cache Layers With Different Defaults

3+ hour, 1+ min ago   (836+ words) Two ZoomEye host searches collected on 18 September 2026 returned 1,551 observable services on port 9200 and 1,462 on port 11211. Port 9200 is Elasticsearch's HTTP interface. Port 11211 is Memcached's default listener. The counts are similar; the security stories are not. Elasticsearch: authentication that became a default…...


dev.to > rafaelbernard > permissions-and-authorisation-a-practical-playbook-bo

Permissions and Authorisation: A Practical Playbook

2+ hour, 49+ min ago   (808+ words) Authorisation is a domain capability, not a collection of scattered endpoint conditionals. For every protected operation, decide consistently whether a verified principal may perform a business action on a specific resource in a defined context—and enforce that decision server-side…...


dev.to > lathelive > we-wanted-a-vercel-supabase-alternative-without-becoming-full-time-devops-1e7f

We wanted a Vercel + Supabase alternative without becoming full-time DevOps

3+ hour, 3+ min ago   (986+ words) When we started building small products, Vercel plus Supabase looked like the obvious stack. It was a good way to get moving. The frontend deployed quickly. Postgres and auth were ready. We did not need to think about servers. Then…...