Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: refreshed concurrency docs, callout webhooks api #1031

Merged
merged 3 commits into from
Dec 19, 2024
Merged

Docs: refreshed concurrency docs, callout webhooks api #1031

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9007208
Update concurrency docs for clarity
djfarrelly Dec 19, 2024
412e35d
Callout the webhooks api
djfarrelly Dec 19, 2024
c8388d4
Disable broken links for now until site is fixed
djfarrelly Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions app/globals.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ body {
--color-border-success: var(--color-matcha-700);
--color-border-error: var(--color-ruby-600);
--color-border-warning: var(--color-honey-600);
--color-border-info: var(--color-purplehaze-700);
--color-border-info: var(--color-breeze-600);

--color-primary-2xSubtle: var(--color-matcha-200);
--color-primary-xSubtle: var(--color-matcha-300);
Expand Down Expand Up @@ -247,7 +247,7 @@ body {
--color-border-success: var(--color-matcha-500);
--color-border-error: var(--color-ruby-300);
--color-border-warning: var(--color-honey-300);
--color-border-info: var(--color-purplehaze-300);
--color-border-info: var(--color-breeze-300);

--color-primary-2xSubtle: var(--color-matcha-800);
--color-primary-xSubtle: var(--color-matcha-700);
Expand Down
2 changes: 1 addition & 1 deletion pages/blog/[slug].tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ const authorURLs = {
"Taylor Facen": "https://twitter.com/ItsTayFay",
"Igor Samokhovets": "https://twitter.com/IgorSamokhovets",
"Dave Kiss": "https://twitter.com/davekiss",
"Bruno Scheufler": "https://brunoscheufler.com",
// "Bruno Scheufler": "https://brunoscheufler.com", // removed while site is disabled
"Lydia Hallie": "https://x.com/lydiahallie",
"Joe Adams": "https://www.linkedin.com/in/josephadams9/",
"Charly Poly": "https://x.com/whereischarly",
Expand Down
2 changes: 1 addition & 1 deletion pages/blog/_posts/sharding-at-inngest.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Our first phase was to create a new interface layer that would coordinate how ou

Two weeks after starting at Inngest, I joined forces with Jack Williams, our founding engineer, and kicked off work on a coordinator service mediating access to the state store. The state store persists events, step outputs, and other metadata on every function run. As users can return blobs and other data from their function run steps, we need to ensure incredibly fast reads and writes to the state store to keep latency as low as possible.

Adding this service boundary would enable connection pooling, centralized instrumentation for observability, and a single cut-over point to roll out changes across different user segments. Long-term, this also allows us to replace the Redis-based storage backend with a more scalable system tailored to our access patterns. If you're interested in our work on the state coordinator, please check out [my recent post](https://brunoscheufler.com/blog/2024-07-04-enhancing-scalability-and-reducing-latency-without-missing-a-beat) on the design decisions and rollout strategy we chose.
Adding this service boundary would enable connection pooling, centralized instrumentation for observability, and a single cut-over point to roll out changes across different user segments. Long-term, this also allows us to replace the Redis-based storage backend with a more scalable system tailored to our access patterns. {/* (NOTE Hidden until Bruno's site is back online) If you're interested in our work on the state coordinator, please check out [my recent post](https://brunoscheufler.com/blog/2024-07-04-enhancing-scalability-and-reducing-latency-without-missing-a-beat) on the design decisions and rollout strategy we chose. */}

## Sharding Redis

Expand Down
Loading
Loading