Anyone know of a transactional email sending service with a nice serverless compatible api client?

J

johtsoOP•4/12/24, 2:50 PM

the whole world of api clients is such a mess..

Ggrimpa Can I have multiple consumers in one Worker, each one processing different queue...

J

johtsoOP•4/12/24, 3:05 PM

docs say "one or more" queues https://developers.cloudflare.com/queues/reference/configuration/#workers

J

johtsoOP•4/12/24, 3:11 PM

@João (grimpa) the name of the queue is in the queue property of the message batch https://developers.cloudflare.com/queues/reference/javascript-apis/#messagebatch

Jjohtso Anyone know of a transactional email sending service with a nice serverless comp...

D

DeChill•4/12/24, 3:56 PM

I'm, using https://resend.com/

N

nachotoday•4/12/24, 4:15 PM

Any good resources for learning about system design using the capability security model used by worker RPCs? The Cap'n proto FAQ links out to http://zesty.ca/capmyths/usenix.pdf which I'm working through, but also would like to see some real world examples.

For instance, the RPC announcement gives the example of an auth service that returns a User stub on auth, allowing the caller to interact with the user only if auth succeeds. Let's say we wanted to add a todo list to the app. So, we spin up a few workers:

- web-srv # binds AuthService
  - fetch routes:
    - GET /todos/<todo-list-id> # get the list
    - PUT /todos/<todo-list-id> # set the list
- todo-srv
  - TodoService: Entrypoint # only accessible by auth-srv
    - todoForUser(user_id): TodoUser
  - TodoUser(user_id): RpcTarget 
    - get(id): string[]
    - set(id, string[])
- auth-srv # binds TodoService
  - AuthService: Entrypoint 
    - checkCookie() : User
  - User(user_id): RpcTarget
    - todos(): TodoUser

- web-srv # binds AuthService
  - fetch routes:
    - GET /todos/<todo-list-id> # get the list
    - PUT /todos/<todo-list-id> # set the list
- todo-srv
  - TodoService: Entrypoint # only accessible by auth-srv
    - todoForUser(user_id): TodoUser
  - TodoUser(user_id): RpcTarget 
    - get(id): string[]
    - set(id, string[])
- auth-srv # binds TodoService
  - AuthService: Entrypoint 
    - checkCookie() : User
  - User(user_id): RpcTarget
    - todos(): TodoUser

- web-srv # binds AuthService
  - fetch routes:
    - GET /todos/<todo-list-id> # get the list
    - PUT /todos/<todo-list-id> # set the list
- todo-srv
  - TodoService: Entrypoint # only accessible by auth-srv
    - todoForUser(user_id): TodoUser
  - TodoUser(user_id): RpcTarget 
    - get(id): string[]
    - set(id, string[])
- auth-srv # binds TodoService
  - AuthService: Entrypoint 
    - checkCookie() : User
  - User(user_id): RpcTarget
    - todos(): TodoUser

- web-srv # binds AuthService
  - fetch routes:
    - GET /todos/<todo-list-id> # get the list
    - PUT /todos/<todo-list-id> # set the list
- todo-srv
  - TodoService: Entrypoint # only accessible by auth-srv
    - todoForUser(user_id): TodoUser
  - TodoUser(user_id): RpcTarget 
    - get(id): string[]
    - set(id, string[])
- auth-srv # binds TodoService
  - AuthService: Entrypoint 
    - checkCookie() : User
  - User(user_id): RpcTarget
    - todos(): TodoUser

So a call sequence might be:

- browser: GET /todos/x Cookie=foo
- web-srv: AuthService.checkCookie(foo) -> User
- web-srv: User.todos() -> TodoUser
- web-srv: TodoUser.get(x) # does this go directly to todo-srv or is there a hop through auth-srv?

- browser: GET /todos/x Cookie=foo
- web-srv: AuthService.checkCookie(foo) -> User
- web-srv: User.todos() -> TodoUser
- web-srv: TodoUser.get(x) # does this go directly to todo-srv or is there a hop through auth-srv?

- browser: GET /todos/x Cookie=foo
- web-srv: AuthService.checkCookie(foo) -> User
- web-srv: User.todos() -> TodoUser
- web-srv: TodoUser.get(x) # does this go directly to todo-srv or is there a hop through auth-srv?

- browser: GET /todos/x Cookie=foo
- web-srv: AuthService.checkCookie(foo) -> User
- web-srv: User.todos() -> TodoUser
- web-srv: TodoUser.get(x) # does this go directly to todo-srv or is there a hop through auth-srv?

Maybe I'm overcomplicating this (a simple todo app certainly doesn't need all this), but I'm curious to see what it looks like to go all-in on the capability model.

A

AKStriker98•4/12/24, 4:36 PM

Question since the docs don’t seem to have this clear, is the ja4 fingerprint included in the ja3_hash bot management variable or is this stored in a different variable?

C

cosbgn•4/12/24, 10:16 PM

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

This means that something like this:

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

Would take very long right?
It would do 6 + 6 + 6 + 6 until it reaches the limit of 50 per request

J

Jonah•4/12/24, 10:20 PM

Does

*domain.com/*

*domain.com/*

*domain.com/*

*domain.com/*

in a Cloudflare worker trigger, no longer process all requests? A few months ago, that trigger pattern ran on every request, domain.com/style.css and so on, now it only runs on / ?

Ccosbgn ``` Concurrent Subrequest Limit As of this release, we impose a limit on the nu...

K

kian•4/12/24, 10:27 PM

Not quite 6+6+6+6

K

kian•4/12/24, 10:27 PM

Once one finishes, another one can start

K

kian•4/12/24, 10:27 PM

It's just 6 concurrent, not batches of 6

Ccosbgn ``` Concurrent Subrequest Limit As of this release, we impose a limit on the nu...

B

bun•4/13/24, 12:32 AM

https://flareutils.pages.dev/promisequeue/ there's an util developed for this specific usecase. runs 6 promises concurrently

PromiseQueue | Flareutils

Small Utilities and little goodies that make developing with Cloudflare easier and faster.

D

dom•4/13/24, 7:58 AM

Workers wrangler logs and realtime logs are not returning anything for a specified worker. Is anyone else experiencing these issues?

D

DeChill•4/13/24, 4:19 PM

Hi, is there any way to trigger workers in response to Messages from an external Kafka topic?

O

oof2win2•4/13/24, 4:58 PM

i dont know if im going insane at this point, but i have this weird scenario. i have a public api and a discord bot that both have the same functionality essentially, so i was thinking that i would take out the core api functionality, put it into a separate worker and make the api and discord bot have bindings to the core functions

O

oof2win2•4/13/24, 4:59 PM

does this make sense? like the main benefit would be that the discord bot wouldnt be using http calls to communicate with the worker

Ooof2win2 does this make sense? like the main benefit would be that the discord bot wouldn...

B

Beny•4/13/24, 5:00 PM

Yes that would be good, no point having 2 copies of the same code

O

oof2win2•4/13/24, 5:01 PM

hmm ill think it over

O

oof2win2•4/13/24, 5:01 PM

might be weird with auth and file uploads

O

oof2win2•4/13/24, 5:01 PM

thanks though, at least im not going insane

O

onnimonni•4/13/24, 7:16 PM

Has someone created tests for scheduled workers with correct typing?

I'm trying to create a test for my scheduled worker and the default typing for a scheduled worker seems to work like this:

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

When I want to call this

scheluded

scheluded

scheluded

scheluded in my test I did this:

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

The typing seems to want an

ScheduledEvent

ScheduledEvent

ScheduledEvent

ScheduledEvent but I didn't find anyway to mock those. The only related mocking function seems to be

createScheduledController

createScheduledController

createScheduledController

createScheduledController but it's type is

 ScheduledController

ScheduledController

 ScheduledController

ScheduledController which is similiar but not the same.

O

onnimonni•4/13/24, 7:17 PM

Second question is that can I somehow test the side effects of the function like what it logs?

The scheduled functions don't return anything so testing the return values is impossible

O

onnimonni•4/13/24, 7:24 PM

Well I was able to fix this by allowing either

ScheduledController

ScheduledController

ScheduledController

ScheduledController or

ScheduledEvent

ScheduledEvent

ScheduledEvent

ScheduledEvent typing in the scheduled event and by following this stackoverflow answer on testing the logging: https://stackoverflow.com/questions/76042978/in-vitest-how-do-i-assert-that-a-console-log-happened

Stack Overflow

In Vitest, how do I assert that a console.log() happened?

The question's in the title. With Jest it was console.log = jest.fn(). How do I get and analyse the console output of the code I'm testing?

Kkian await scheduler.wait(ms)

S

Shravan•4/13/24, 11:21 PM

is there any difference between scheduler.wait and

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

and how they work in workers?

SShravan is there any difference between scheduler.wait and `export const sleep = (ms: n...

B

Beny•4/14/24, 12:23 AM

I think it fixes Date.now() if I remember correctly

BBeny I think it fixes Date.now() if I remember correctly

S

Shravan•4/14/24, 1:29 AM

you mean if we use date.now after scheduler.wait?

U

Unsmart•4/14/24, 1:34 AM

Its just an awaitable alternative of setTimeout. So its basically exactly the same.

A

Armaan from Armenia•4/14/24, 6:54 AM

how do I get rid of this for the dev to challenge?

A

Armaan from Armenia•4/14/24, 6:54 AM

deadline is 6 minutes away and I used it all

A

Armaan from Armenia•4/14/24, 6:54 AM

help

AArmaan from Armenia how do I get rid of this for the dev to challenge?

O

onnimonni•4/14/24, 9:01 AM

Read the error. You have already used your free quota. Sign up for the paid workers plan for 5$. You can stop using it when you don't need it anymore.

Oonnimonni Read the error. You have already used your free quota. Sign up for the paid work...

A

Armaan from Armenia•4/14/24, 9:20 AM

Thank you so much! Updated!:D

M

Migmac•4/14/24, 12:50 PM

Where can I submit a feature-request / extension / suggestion?

E

Erisa•4/14/24, 12:51 PM

#workers-feature-suggestions

M

Migmac•4/14/24, 12:51 PM

Thank yoU!

N

neoney•4/14/24, 8:28 PM

Worker supposed to run every minute on cron

all recent triggers have been erroring, trying to debug, does not seem to be running anymore

N

neoney•4/14/24, 8:29 PM

ive been tailing for 6 minutes

N

neoney•4/14/24, 8:29 PM

no logs

N

neoney•4/14/24, 8:30 PM

does tail not show logs from cron?

W

Walshy•4/14/24, 8:38 PM

tail does show

W

Walshy•4/14/24, 8:39 PM

Are you on a paid plan?

W

Walshy•4/14/24, 8:39 PM

you're averaging a lot of cpu time per execution

WWalshy Are you on a paid plan?

N

neoney•4/14/24, 8:47 PM

yes

WWalshy you're averaging a lot of cpu time per execution

N

neoney•4/14/24, 8:47 PM

yeah its a worker that goes through all database stuff that hasnt been processed and sends webhooks

N

neoney•4/14/24, 8:47 PM

ive added a try catch over the main functions

N

neoney•4/14/24, 8:47 PM

and deployed it

N

neoney•4/14/24, 8:47 PM

suddenly its green, and i have logs

N

neoney•4/14/24, 8:48 PM

and no logs errored

N

neoney•4/14/24, 8:48 PM

:thinkRoll:

Anyone know of a transactional email sending service with a nice serverless compatible api client?

Similar Threads

Similar Threads

Similar Threads