RavenDB 7.0 Released: AWS SQS & AWS Lambda integration

The big-ticket item for RavenDB 7.0 may be the new vector search and AI integration, but those aren’t the only new features this new release brings to the table.AWS SQS ETL allows you to push data directly from RavenDB into an SQS queue. You can read the full details in our documentation, but the basic idea is that you can supply your own logic that would push data from RavenDB documents to SQS for additional processing.For example, suppose you need to send an email to the customer when an order is marked as shipped. You write the code to actually send the email as an AWS Lambda function, like so:def lambda_handler(event, context): for record in event['Records']: message_body = json.loads(record['body']) email_body = """ Subject: Your Order Has Shipped! Dear {customer_name}, Great news! Your order #{order_id} has shipped. Here are the details: Track your package here: {tracking_url} """.format( customer_name=message_body.get('customer_name'), order_id=message_body.get('order_id'), tracking_url=message_body.get('tracking_url') ) send_email( message_body.get('customer_email'), email_body ) sqs_client.delete_message( QueueUrl=shippedOrdersQueue, ReceiptHandle=record['receiptHandle'] )You wire that to the right SQS queue using:aws lambda create-event-source-mapping \ --function-name ProcessShippedOrders \ --event-source-arn arn:aws:sqs:$reg:$acc:ShippedOrders \ --batch-size 10The next step is to get the data into the queue. This is where the new AWS SQS ETL inside of RavenDB comes into play. You can specify a script that reacts to changes inside your database and sends a message to SQS as a result. Look at the following, on the Orders collection:if(this.Status !== 'Completed') return; const customer = load(this.Customer); loadToShippedOrders({ 'customer_email': customer.Email, 'customer_name': customer.Name, 'order_id': id(this), 'tracking_url': this.Shipping.TrackingUrl });And you are… done! We have a full blown article with all the steps walking you through configuring both RavenDB and AWS that I encourage you to read.Like our previous ETL processes for queues, you can also use RavenDB in the Outbox pattern to gain transactional capabilities on top of the SQS queue. You write the messages you want to reach SQS as part of your normal RavenDB transaction, and the RavenDB SQS ETL will ensure that they reach the queue if the transaction was successfully committed.

Mar 3, 2025 - 16:01

The big-ticket item for RavenDB 7.0 may be the new vector search and AI integration, but those aren’t the only new features this new release brings to the table.

AWS SQS ETL allows you to push data directly from RavenDB into an SQS queue. You can read the full details in our documentation, but the basic idea is that you can supply your own logic that would push data from RavenDB documents to SQS for additional processing.

For example, suppose you need to send an email to the customer when an order is marked as shipped. You write the code to actually send the email as an AWS Lambda function, like so:

def lambda_handler(event, context):
    for record in event['Records']:
        message_body = json.loads(record['body'])
        
        email_body = """
Subject: Your Order Has Shipped!


Dear {customer_name},
Great news! Your order #{order_id} has shipped. Here are the details:
Track your package here: {tracking_url}
""".format(
            customer_name=message_body.get('customer_name'),
            order_id=message_body.get('order_id'),
            tracking_url=message_body.get('tracking_url')
        )
        
        send_email(
            message_body.get('customer_email'),
            email_body
        )
        
        sqs_client.delete_message(
            QueueUrl=shippedOrdersQueue,
            ReceiptHandle=record['receiptHandle']
        )

You wire that to the right SQS queue using:

aws lambda create-event-source-mapping \
--function-name ProcessShippedOrders \
--event-source-arn arn:aws:sqs:$reg:$acc:ShippedOrders \
--batch-size 10

The next step is to get the data into the queue. This is where the new AWS SQS ETL inside of RavenDB comes into play.

You can specify a script that reacts to changes inside your database and sends a message to SQS as a result. Look at the following, on the Orders collection:

if(this.Status !== 'Completed') return;


const customer = load(this.Customer);
loadToShippedOrders({
  'customer_email': customer.Email,
  'customer_name': customer.Name,
  'order_id':        id(this),
  'tracking_url': this.Shipping.TrackingUrl
});

And you are… done! We have a full blown article with all the steps walking you through configuring both RavenDB and AWS that I encourage you to read.

Like our previous ETL processes for queues, you can also use RavenDB in the Outbox pattern to gain transactional capabilities on top of the SQS queue. You write the messages you want to reach SQS as part of your normal RavenDB transaction, and the RavenDB SQS ETL will ensure that they reach the queue if the transaction was successfully committed.