-
Notifications
You must be signed in to change notification settings - Fork 308
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Main change that fix memory leak: queue/inmemory replace backing slice with ring buffer implementation. Key change preventing memory leaks: set reference for removed event to nil to release memory User Recognition: separate pipelines for anonymous and identified events. aggregate identified events before processing - to speed up recognition phase. reduce users_recognition.pool.size to 5 to increase effectiveness of identifier aggregation don't copy every anonymous event to push them into queue. instead serialize to compressed bytes don't mutate event for User-Agent bot detection Optimize memory allocations while manipulating objects Don't apply babel for builtin transform - to avoid goja initialization Batch processing: do not copy events data for the first destination mapped to token
- Loading branch information
Showing
42 changed files
with
384 additions
and
341 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
title: Overview | ||
--- | ||
|
||
# Extending Jitsu | ||
|
||
With [Jitsu SDK](https://github.com/jitsucom/jitsu) you can implement extension for Jitsu using Typescript. Each extension | ||
is a separate node package that could be published to public or private npm repository. Jitsu server downloads extension code and executes in within internal | ||
V8 JS virtual machine | ||
|
||
Extensions can have several purposes: | ||
|
||
* **[Destination](/docs/extending/destination-plugins)**. An external service where Jitsu distributes | ||
incoming events based on configuration. A good example of the destination extension will be [Mixpanel](https://github.com/jitsucom/jitsu-mixpanel). | ||
* **Source (coming soon)**. Source (or pull-source) is typically a service or platform from which Jitsu pulls the data. Later, the data is being | ||
sent to destination database or data-warehouse. See the list of [all supported source](https://cloud.jitsu.com/sources). The support of sources in | ||
Jitsu SDK is coming in **Mar 2022** |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,24 @@ | ||
# OpenAPI | ||
# API Specs | ||
|
||
Jitsu exposes following HTTP API | ||
|
||
## Configuration API | ||
|
||
This API is for configuring Jitsu: adding/removing/editing sources, destinations, api keys and etc. | ||
All operations available in Jitsu UI can be done with the API too. In fact, UI is talking with backend | ||
using the very same API | ||
|
||
<LargeLink | ||
href="/configurator-openapi.html" | ||
title="Jitsu Configurator API described in openapi specification" | ||
/> | ||
title="Jitsu Configurator API" | ||
/> | ||
|
||
## Jitsu Server API | ||
|
||
Jitsu Server API is documentation is coming. We're in the process of migrating documentation | ||
to Open API spec. So far the documentation is scattered across different sections of documentation: | ||
|
||
* [Cluster Administration API](/docs/other-features/admin-endpoints) | ||
* [Events Cache API](/docs/other-features/events-cache) | ||
* [Event API](/docs/sending-data/api) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,69 +1,3 @@ | ||
{ | ||
"sections": [ | ||
{ | ||
"name": "🚀 Quick Start", | ||
"pages": [ | ||
"deployment", | ||
"changelog" | ||
] | ||
}, | ||
{ | ||
"name": "Jitsu Internals", | ||
"pages": [ | ||
"internals/jitsu-server" | ||
] | ||
}, | ||
{ | ||
"name": "Sending data", | ||
"pages": [ | ||
"sending-data/js-sdk", | ||
"sending-data/node-js", | ||
"sending-data/mobile-apps", | ||
"sending-data/api", | ||
"sending-data/bulk-api", | ||
"sending-data/segment-api", | ||
"sending-data/segment-integration", | ||
"sending-data/gif-pixel-api", | ||
"sending-data/mobile-api", | ||
"sending-data/javascript-reference" | ||
] | ||
}, | ||
{ | ||
"name": "Server Configuration", | ||
"pages": [ | ||
"configuration", | ||
"destinations-configuration", | ||
"sources-configuration", | ||
"sources" | ||
] | ||
}, | ||
{ | ||
"name": "Extending Jitsu", | ||
"pages": [ | ||
"extending/destination-plugins" | ||
] | ||
}, | ||
{ | ||
"name": "Configurator UI", | ||
"pages": [ | ||
"configurator-configuration" | ||
] | ||
}, | ||
{ | ||
"name": "❤️ Features", | ||
"pages": [ | ||
"other-features/segment-compatibility", | ||
"other-features/dbt-cloud-integration", | ||
"other-features/dry-run-events", | ||
"other-features/retroactive-user-recognition", | ||
"other-features/events-cache", | ||
"other-features/geo-data-resolution", | ||
"other-features/typecast", | ||
"other-features/admin-endpoints", | ||
"other-features/application-metrics", | ||
"other-features/cli", | ||
"other-features/jitsu-api" | ||
] | ||
} | ||
] | ||
} | ||
"__MOVED__": "This file has been moved to jitsu.com/components/documentation/DocumentationTableOfContents.json. Edit it there" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.