One Small Change Made My Failing Email System Work Perfectly: While sending joining reminders, emails were failing on the cloud — they kept timing out even though the code logic was correct. The problem: Every email was creating a new SMTP connection inside a loop. Example: 1 candidate → 2 emails → each iteration = 2 connections. This was overloading the server and causing timeouts. The solution: Create the SMTP transporter once and reuse it for all emails Send all emails in parallel using Promise.all The results were immediate: ✅ Emails now send reliably on the cloud ✅ Execution is much faster ✅ Resources are used efficiently and errors are gone 💡 Lesson learned: A tiny, well-placed optimization can turn a failing system into a scalable, production-ready engine. #NodeJS #BackendOptimization #AsyncProgramming #ScalableSystems #SoftwareEngineering #ProblemSolving #DeveloperJourney
Optimizing Email System with Reused SMTP Transporter and Parallel Execution
More Relevant Posts
-
Most performance problems aren’t caused by slow queries. They’re caused by avoidable ones. In this talk, I walk through a sample Aspire based application and show how small, boring decisions add up: 1. Using Includes to stop N+1s before they exist 2. Batching multiple queries with LazyAsync so the server is hit once 3. ETags to reduce cloud egress instead of paying for the same bytes sent over and over again. If you care about predictable behavior, lower costs, and fewer surprises in production, jump directly to the lazy, caching and more: https://lnkd.in/dNcSvnuz #dotnet #performance #database #Aspire #RavenDB
-
Managing files across S3, FTP, SFTP, Dropbox, and local storage shouldn't mean juggling five different interfaces. Filestash is an open source file manager that gives you one unified interface for all your storage backends. Here's what makes it powerful: → Connect multiple cloud services and protocols through a single dashboard → Give clients or team members secure file access without sharing credentials → Build custom workflows with plugins while keeping everything self-hosted You can try it for free on Open Source Cloud – no credit card required. 🔗 Try it: https://lnkd.in/dkttpvWs 📖 Docs: https://lnkd.in/dSRyfs6X 💻 GitHub: https://lnkd.in/dyBKbAPT #opensource #storage #filemanagement #cloudservices #developertools #selfhosted #s3 #devops
-
Access control shouldn’t be a full-time job. Passage is CTO2B’s open-source access control management solution, built to simplify cloud access across platforms like AWS, GitLab, and Google Workspace. You define roles once, users request access in one place, and time-limited permissions auto-expire so least-privilege stays real as teams grow. Download Passage from here: https://lnkd.in/dsyy36wJ
-
-
🚀 Want an easy way to deploy your apps to the cloud? Railway is a platform that lets developers deploy their software to production without dealing with complicated infrastructure. It’s ideal for backends, APIs, databases, and more — all with a clean visual dashboard. 💡 Why it’s worth trying: ✔️ Connect your GitHub / code — Railway handles the rest ✔️ Automatic setup (network, SSL, scaling) ✔️ Built-in database & logs support — minimal configuration 🔗 Check it out here ➤https://lnkd.in/deg776Qu
-
GCP Mini Project – Compute Engine Web Server [Part-2]. Following up on my previous post, here’s a short video walkthrough of my GCP Compute Engine web server project. ☁️ This video demonstrates: 1.The working website 2.External and static IP configuration 3. Live server deployment on GCP This project helped me strengthen my understanding of cloud infrastructure, networking, and server management through hands-on implementation. Looking forward to building more scalable and automated cloud solutions 🚀 #GoogleCloud #CloudProjects #DevOps #CloudEngineer #TechJourney
-
Tree Structure for a terraform project: 📁 my-terraform-project/ The root directory. This is home base for all your configuration files. 📄 providers.tf Your "translators". This file defines which cloud providers (AWS, Azure, GCP, etc.) you need and locks their versions. 📄 variables.tf The placeholders. Declare all your inputs here. Think of these as the questions your project asks before it builds anything ("What region should this be in?"). 📄 terraform.tfvars The answers. This file holds the actual values for your variables. Keep your stage environment values separate from production here! 📄 main.tf The main event. All your actual infrastructure (servers, databases, networks) is defined here. This is where you declare your resources. 📄 outputs.tf The results. This file displays important information after a successful deployment, like a server's IP address or connection strings.
-
-
🚀 Async in .NET: await task; await task; vs await Task.WhenAll() — what’s the real difference? If you work with async/await in .NET (Core / .NET 6+), this small detail can have a big impact on performance 👀 #dotnet #csharp #asyncawait #performance #backend #cloud #softwareengineering
-
Why I’m choosing "No Servers" in 2026 🚀 The biggest shift in cloud strategy isn't just about moving to the cloud—it’s about moving away from managing it. For a long time, "Serverless" was seen as a niche for small APIs or simple cron jobs. Today, it’s the default for teams that want to move at the speed of their ideas. Why are we seeing the massive migration to AWS Serverless? • Zero "Janitor Work": Stop patching OS kernels and managing SSH keys. AWS handles the maintenance; you handle the features. • Scale that Breathes: Whether you have 10 users or 10 million, services like Lambda and DynamoDB expand and contract instantly. No more "over-provisioning" just in case. • True Pay-per-Value: If your code isn't running, you aren't paying. It’s the difference between renting an empty building and only paying for the desk space you use. The 2026 Reality Check: Yes, "Cold Starts" are still a thing, and yes, at massive constant scale, EC2 might be cheaper on paper. But for most businesses, the Total Cost of Ownership (TCO) of serverless wins because your developers are building products, not babysitting infrastructure. Stop managing servers. Start managing value. 💡 #AWS #Serverless #CloudComputing #SoftwareEngineering #TechTrends2026 #AWSLambda
-
While everyone pushes “cloud or nothing”, we chose something better: freedom 🕊 On-premise or cloud, the decision stays where it belongs: with the customer. Some teams want full control of their infrastructure. Others prefer the simplicity of managed services and the perks that come with it, like real-time debugging logs and automatic updates. What matters isn’t where your data lives, but how easily you can work, troubleshoot, and grow. Flexibility isn’t a compromise, it’s the smartest way to stay in control 🔓 TICGAL
-
Day 10 of the #100DaysCloudChallenge: Keeping Things Stable on the Cloud 🌐📍 I made it to day 10! Today, I worked on making sure our application always has the same address online using AWS Elastic IPs. What I Did: I linked an Elastic IP (xfusion-ec2-eip) that I already had to our xfusion-ec2 server in the us-east-1 area. Why This Is Important: Usually, AWS public IPs can change. If you turn off your server to save money or fix something, you lose the IP address. With an Elastic IP, we have a fixed address. This is important for things like DNS records and whitelisting. It means people can always find us at the same spot, even if we make changes. Cool Things I Learned: ✅ IPs Separate from Servers: I now know that Elastic IPs are separate from the servers they're connected to. ✅ Quick Change: The change happened right away without needing to restart the server. ✅ CLI Skills: I used commands like describe-addresses and associate-address to do the linking quickly. Learning consistently for 10 days has really changed how I view cloud stuff. Let's go to Day 11! #AWS #ElasticIP #Networking #DevOps #100DaysOfCloud #CloudMigration #Infrastructure #Milestone #TechLearning
-
