OWOWASP · Open source
Community homeHot discussions Latest posts Best of Knowledge base Resources About

OWASP · Open source · Building an internal platform with owasp-opensource from scratch: architecture and decision log

43
OWr/owasp-opensource·posted by ran_bo·2 days agoHelp

Building an internal platform with owasp-opensource from scratch: architecture and decision log

Some background first. Our setup is owasp-opensource plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

Worth noting: the official docs do cover this, just in a very inconspicuous spot. I only found it reading the source comments, where the author explains the reasoning — roughly "so that it degrades into predictable behaviour in extreme cases".

Self-host — full control44%
Managed service — less work28%
Hybrid: core self-hosted17%
Not decided yet11%

73 votes total

20 comments

20 comments

M
Lli_ming·2 days agoedited

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

341
Mmike_xu·1 hour agoedited

Saved. I am reworking this area this week — this saves a lot of wrong turns.

230
Kkite·2 days ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

336
Rrase·just now

This is not a owasp-opensource problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

74
Sslow_query·3 minutes ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

127
Llinlin·3 minutes ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

79
Mmike_xu·1 hour ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

457
Zzhou_yi·2 hours ago

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

311
Oops_wang·3 minutes agoedited

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

340
Wwinter·1 hour ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

1
Hhuang_ke·28 minutes agoedited

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

150
Ddev_zhou·28 minutes ago

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

41
Wwinter·12 minutes ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

12
Rrase·28 minutes agoedited

I just read the owasp-opensource source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

68
Wwinter·just now

This is not a owasp-opensource problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

64
Ddev_zhou·2 days ago

One counter-example: below owasp-opensource 7.4 the semantics of that code are different, so do not copy it verbatim. We got burned in staging and rolled back once.

1
Lli_ming·3 minutes ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

48
Nnikic·5 hours agoedited

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

43
Zzhu_zong·3 minutes ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

40
Lli_ming·2 days ago

Saved. I am reworking this area this week — this saves a lot of wrong turns.

1

This is the post detail page /en/c/owasp-opensource/post/p5. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →