Every .NET microservices project hits the same 5 problems Most teams pull in 5 different libraries to solve them There is a better way. I rebuilt a hotel booking system with 4 microservices last week. In a typical setup I would need: → MassTransit for messaging → Polly for retries → Refit HttpClient for service calls → A Vault client for secrets → A Redis SDK for caching and locks Five SDKs. Five config styles. Five mental models. Instead, I used Dapr - one runtime, one client, one consistent API. Here are the 5 problems and how Dapr solves each: 𝟭. 𝗦𝗲𝗿𝘃𝗶𝗰𝗲-𝘁𝗼-𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝗰𝗮𝗹𝗹𝘀 You reference services by App ID instead of URLs. 𝚊𝚠𝚊𝚒𝚝 𝚍𝚊𝚙𝚛𝙲𝚕𝚒𝚎𝚗𝚝.𝙸𝚗𝚟𝚘𝚔𝚎𝙼𝚎𝚝𝚑𝚘𝚍𝙰𝚜𝚢𝚗𝚌("𝚑𝚘𝚝𝚎𝚕𝚜-𝚊𝚙𝚒", "𝚛𝚘𝚘𝚖𝚜/𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎"); Dapr handles service discovery, retries, and tracing. No hardcoded URLs anywhere. 𝟮. 𝗔𝘀𝘆𝗻𝗰 𝗲𝘃𝗲𝗻𝘁𝘀 Publish events with one line: 𝚊𝚠𝚊𝚒𝚝 𝚍𝚊𝚙𝚛𝙲𝚕𝚒𝚎𝚗𝚝.𝙿𝚞𝚋𝚕𝚒𝚜𝚑𝙴𝚟𝚎𝚗𝚝𝙰𝚜𝚢𝚗𝚌("𝚙𝚞𝚋𝚜𝚞𝚋", "𝚋𝚘𝚘𝚔𝚒𝚗𝚐-𝚌𝚛𝚎𝚊𝚝𝚎𝚍", 𝚎𝚟𝚝); Subscribers handle them via the [Topic] attribute. No more BackgroundService boilerplate code. 𝟯. 𝗦𝘁𝗮𝘁𝗲 𝗮𝗻𝗱 𝗰𝗮𝗰𝗵𝗶𝗻𝗴 Key/value storage with pluggable backends: 𝚊𝚠𝚊𝚒𝚝 𝚍𝚊𝚙𝚛𝙲𝚕𝚒𝚎𝚗𝚝.𝚂𝚊𝚟𝚎𝚂𝚝𝚊𝚝𝚎𝙰𝚜𝚢𝚗𝚌("𝚜𝚝𝚊𝚝𝚎𝚜𝚝𝚘𝚛𝚎", 𝚔𝚎𝚢, 𝚟𝚊𝚕𝚞𝚎); ↳ Want TTL? Pass metadata. ↳ Want optimistic locking? Use ETags. ↳ Backend can be Redis, PostgreSQL, or Cosmos DB. 𝟰. 𝗦𝗲𝗰𝗿𝗲𝘁𝘀 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 No more credentials in appsettings: 𝚟𝚊𝚛 𝚜𝚎𝚌𝚛𝚎𝚝𝚜 = 𝚊𝚠𝚊𝚒𝚝 𝚍𝚊𝚙𝚛𝙲𝚕𝚒𝚎𝚗𝚝.𝙶𝚎𝚝𝚂𝚎𝚌𝚛𝚎𝚝𝙰𝚜𝚢𝚗𝚌("𝚜𝚎𝚌𝚛𝚎𝚝𝚜𝚝𝚘𝚛𝚎", "𝚙𝚊𝚢𝚖𝚎𝚗𝚝-𝚐𝚊𝚝𝚎𝚠𝚊𝚢"); Backend can be Azure Key Vault, AWS Secrets Manager, or HashiCorp Vault. Application code stays identical across environments. 𝟱. 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗹𝗼𝗰𝗸𝘀 Mutual exclusion across service instances: 𝚟𝚊𝚛 𝚕𝚘𝚌𝚔𝚁𝚎𝚜𝚙𝚘𝚗𝚜𝚎 = 𝚊𝚠𝚊𝚒𝚝 𝚍𝚊𝚙𝚛𝙲𝚕𝚒𝚎𝚗𝚝.𝙻𝚘𝚌𝚔("𝚜𝚝𝚊𝚝𝚎𝚜𝚝𝚘𝚛𝚎", "𝚛𝚘𝚘𝚖-𝟷𝟶𝟷", "𝚘𝚠𝚗𝚎𝚛", 𝟹𝟶); Safely reserve a room when 3 service instances race for it. The killer feature is what ties them all together. Every name (pubsub, statestore, secretstore) maps to a YAML component file. Switch RabbitMQ to Kafka by editing one file. Application code never changes. I wrote a full hands-on guide with the complete hotel booking implementation: → Sidecar architecture explained → AppHost setup with .NET Aspire 13 → Pub/sub between Bookings and Payments → Service invocation between Bookings and Hotels → State management for room availability caching → The DaprConstants pattern I use across all services 📌 Read the full guide here: ↳ antondevtips.com/blog/gettin… —— ♻️ Repost to help other .NET developers build cloud-native systems ➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills

लंच के बाद वॉशरूम में जाकर अपनी सूंघी हुई पैंटी छुपाकर रखना, ताकि फिर कभी काम में ताजगी पा सकूं। #PantyCache #ScentHoarder #SecretStore #OfficeRefresh #NSFWHindi

I wanted to create a project in Rust to learn more about building real-world tools. So I built a simple version of a password manager — SecretStore 🔐 ✨ A CLI tool for securely storing your credentials 🔒 Encrypts your data, master password protected github.com/HarwaniDev/Secret…

"I see you watch Dragons' Den" without telling me you do 😂 #Littles #Coffee #SecretStore

DevOps Project: Secrets Management in Kubernetes with AWS Secrets Manager & External Secrets This project will guide you through setting up secure secrets management in Kubernetes using AWS Secrets Manager and External Secrets Operator to keep sensitive data safe. Project Steps: 1) Set Up AWS Secrets Manager 1. Create a new secret in AWS Secrets Manager (e.g., a database password or API key). 2. Use a key-value pair format (e.g., DB_PASSWORD=mysecurepassword). 3. Enable automatic secret rotation if required. 4. Copy the ARN (Amazon Resource Name) of the secret for later use. 2) Configure IAM Permissions for Kubernetes 1. Create an IAM role for Kubernetes service accounts. 2. Attach the SecretsManagerReadOnly policy to allow access to AWS Secrets Manager. 3. Use IAM OIDC provider to associate the IAM role with the Kubernetes cluster. 4. Create a Kubernetes service account and associate it with the IAM role. 3) Install External Secrets Operator in Kubernetes 1. Deploy External Secrets Operator using Helm 2. Verify that the External Secrets Operator pods are running. 4) Configure External Secret Resource in Kubernetes 1. Create a SecretStore object in Kubernetes to connect to AWS Secrets Manager. 2. Reference the IAM role associated with the Kubernetes service account. 3. Define an ExternalSecret resource that: • Links to the AWS Secrets Manager secret ARN. • Maps the AWS secret values to a Kubernetes secret. 4. Apply the configuration using kubectl apply -f external-secret.yaml. 5) Use the Secrets in Kubernetes Pods 1. Create a Kubernetes Deployment that references the synced secret. 2. Mount the secret as an environment variable or volume in the pod. 3. Deploy the application and verify it can access the secret securely. 6) Secure & Monitor Secret Usage 1. Enable AWS CloudTrail to log access to AWS Secrets Manager. 2. Restrict Kubernetes API access to secrets using RBAC (Role-Based Access Control). 3. Regularly audit Kubernetes Secrets and IAM policies to minimize risk. 4. Rotate secrets automatically in AWS Secrets Manager and ensure Kubernetes updates them dynamically. By following these steps, you'll implement a secure and automated secrets management system in Kubernetes while leveraging AWS Secrets Manager and External Secrets Operator.

このネックウォーマー 藍サポ SECRETSTOREだと 送料込みで1350円✨ 届いた日の午後に中川聖也選手が使ってるのを発見✨ 息子の野球教室用に買ったけど 軽くて温かくて私も欲しいからもうひとつ買おうかな 2025シーズン選手名鑑撮影の裏側！youtu.be/zWZLkoazOm4?si=7mMD… @YouTubeより

おうちKubernetesクラスタの全Namespaceに配置していたSecretStoreをClusterSecretStoreに置き換えてシンプルな構成にしました😀 これを→こう external-secrets.io/latest/a…

Managing secrets in Kubernetes just got simpler! 💡 With External Secrets, you can securely sync secrets from cloud providers like AWS, Azure, and Google Cloud into your Kubernetes cluster. Here’s how it works: ➢ Set up SecretStore or ClusterSecretStore to define where your secrets are stored externally. ➢ Use ExternalSecret as a blueprint to create Kubernetes secrets. ➢ Sync everything via Helm, and you’re good to go! No more manual secret management—super secure and scalable! 🔐 #Kubernetes #SecretsManagement #CloudNative #DevOps #AWS #Azure #GCP

Released my 3⃣rd blog post abt @crossplane_io🍦& @argoproj🐙: How to integrate them with #ExternalSecrets #Operator @XSecretsInc 🔐 codecentric.de/wissens-hub/b… for ANY external #SecretStore (I chose @doppler 👈 Have fun reading! cc @codecentric @upbound_io @akuityio #Vault #KeyVault

los cara a cara es la sala de los videos como la de secretstore #GH25S

Il fallait être là. Ça c’était du #SecretStory qui SecretStore

Sealed Secrets to store ESO SecretStore credentials for Hashicorp Vault in Git. ESO for #K8S Secret management.

日本人 Secret Store🛍️ 新しく出品しております〜！ 観てみて下さい！！ #日本人secretstore

#Dapr secret store component demonstration using Minikube with a #PowerShell app youtu.be/zTp6Aj-2LJI #AzureKeyVault #SecretStore #Dapr #PowerShell #Microservices #Minikube #Pode #PSHTML

El jueves pasado estuve haciendo la columna de sexologia de @animalesderadio Hablamos de placer femenino y nos acompañaron los.productos de @secretstore #sexualidad #educaciónsexual #juguetessexuales

dios bendiga a secretStore y pueda ganar un sorteo 🥺😂

What are your thoughts on adding SecretManagement and SecretStore as part of PS7 package? We're looking for feedback here: github.com/PowerShell/PowerS…

Mapunto. Como buen murciano, contad con mi acho.

🟠 .secretstore/ Sold for 500 $HNS (58 USD) #Secretstore #Handshake #HNS

うーん、Azure Key Vault と Kubernetes は相性が悪いのかな‥SecretStore リソース作るのに ClientID と ClientSecret を必要とする。これは terraform で登録して取得可能だけど、SecretStore リソースのための Secret リソースだけ動的に作らないといけないのか‥