<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>NotifySetu Engineering Blog</title>
        <link>https://www.notifysetu.com</link>
        <description>System architecture, notification failover routing, and developer updates.</description>
        <lastBuildDate>Thu, 06 Aug 2026 03:25:06 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>NotifySetu Engineering Blog</title>
            <url>https://www.notifysetu.com/favicon.ico</url>
            <link>https://www.notifysetu.com</link>
        </image>
        <copyright>All rights reserved 2026, NotifySetu</copyright>
        <item>
            <title><![CDATA[Architecting a Resilient Multi-Provider Fallback Engine for Notifications]]></title>
            <link>https://www.notifysetu.com/blog/architecting-resilient-multi-provider-fallback-engine</link>
            <guid>https://www.notifysetu.com/blog/architecting-resilient-multi-provider-fallback-engine</guid>
            <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Deep dive into how NotifySetu handles provider outages, rate limit spikes, and automatic fallback routing in Spring Boot microservices.]]></description>
            <content:encoded><![CDATA[
When your product scales to millions of users, notification delivery failure is not just an inconvenience — it directly impacts revenue and user trust. Password reset OTPs that arrive 5 minutes late lead to abandoned logins, while delayed transactional emails degrade customer experience.

In this technical breakdown, we share the engineering architecture behind NotifySetu's zero-downtime provider fallback engine.

## The Multi-Provider Challenge

Most legacy notification systems bind code directly to a single provider API SDK (such as SendGrid or Twilio). However, single providers inevitably experience:
1. **Regional Outages:** Cloud infrastructure or carrier route failures.
2. **Rate Limit Throttling:** Unexpected traffic bursts triggering 429 Too Many Requests.
3. **Carrier Rejections:** Strict regulatory filters (such as DLT in India) blocking specific SMS templates.

## The NotifySetu Fallback Circuit Breaker

NotifySetu decouples the dispatch request from specific provider implementations. When an application calls `/v1/notifications/send`, the platform executes a 3-step routing pipeline:

1. **Health Verification:** Checks the real-time circuit breaker status of the primary provider (e.g., SendGrid).
2. **Dispatch Attempt:** Sends payload over TLS 1.3 with a 500ms timeout budget.
3. **Automatic Reroute:** If primary returns 5xx or times out, the payload is immediately handed to the secondary provider (e.g., AWS SES or Plivo).

```json
{
  "routingPolicy": {
    "primary": "SENDGRID",
    "fallbacks": ["AWS_SES", "MAILGUN"],
    "maxLatencyMs": 500
  }
}
```

## Results & Benchmarks

In production tests, automatic failover reduced failed notification dispatches from **1.4% to less than 0.001%** across 50 million dispatches.
]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Official Meta WhatsApp Cloud API Support]]></title>
            <link>https://www.notifysetu.com/blog/introducing-meta-whatsapp-cloud-api-adapter</link>
            <guid>https://www.notifysetu.com/blog/introducing-meta-whatsapp-cloud-api-adapter</guid>
            <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Send rich interactive WhatsApp dispatches with quick-reply buttons and media templates directly through Meta Graph API.]]></description>
            <content:encoded><![CDATA[
We are thrilled to announce native support for the Meta WhatsApp Cloud API inside NotifySetu!

WhatsApp has quickly become the primary communication channel for transaction updates, shipping alerts, and authentication OTPs across Latin America, India, Europe, and Southeast Asia.

## Key Features

- **Direct Meta Integration:** Zero middleman markup fees.
- **Interactive Button Templates:** Support for Quick Replies and CTA URLs.
- **Media Attachments:** Send invoices as PDFs or order receipts as high-res images.
- **24-Hour Customer Support Window:** Automated session state management.
]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transactional Email Deliverability Best Practices in 2026]]></title>
            <link>https://www.notifysetu.com/blog/transactional-email-deliverability-best-practices-2026</link>
            <guid>https://www.notifysetu.com/blog/transactional-email-deliverability-best-practices-2026</guid>
            <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Essential rules for maintaining 99%+ inbox placement with strict SPF, DKIM, and DMARC enforcement.]]></description>
            <content:encoded><![CDATA[
Email providers (Gmail, Yahoo, Outlook) have significantly tightened spam filtering algorithms. Unaligned domain signatures can result in instant spam box placement or outright rejection.

## Core Rules for 2026

1. **Enforce Strict DMARC Policy:** Set your DMARC record to `p=reject` or `p=quarantine`.
2. **Dedicated Subdomains for Notifications:** Use `mail.yourdomain.com` or `notifications.yourdomain.com` instead of root domain.
3. **Warm Up Dedicated IPs:** Gradually ramp up volume over 4 weeks when provisioning new provider IP pools.
]]></content:encoded>
        </item>
    </channel>
</rss>