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.

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

Enhance state-indexer compatibility with NEAR Lake and NEAR Indexer Framework #188

Closed
Tracked by #186
khorolets opened this issue Feb 28, 2024 · 4 comments
Closed
Tracked by #186
Assignees
Labels
enhancement New feature or request performance

Comments

@khorolets
Copy link
Member

To improve the efficiency and responsiveness of ReadRPC, we aim to make the state-indexer compatible with both NEAR Lake and NEAR Indexer Framework. NEAR Lake-based indexers are known for their lightweight design, cost-effectiveness, and ease of maintenance. However, they inherently introduce a ~3-second delay in data transfer to clients via S3. To address this, we propose developing different state-indexer binaries: one for NEAR Lake and another for the NEAR Indexer Framework. This approach will allow us to maintain the advantages of NEAR Lake while significantly reducing data transfer delays by leveraging a nearcore-based state-indexer.

The ultimate goal is to provide ReadRPC and regular RPC node users with the most recent data, mimicking the immediacy expected from NEAR's native RPC.

@khorolets
Copy link
Member Author

I've realized that having the state-indexer built on top of nearcore in the ReadRPC fleet of machines would allow us to redirect write-requests or regular RPC proxies to that node, offloading the Pagoda's RPC service a bit 🤔

@kobayurii
Copy link
Member

#189

github-merge-queue bot pushed a commit to near/nearcore that referenced this issue Mar 1, 2024
…ng Optimistic Blocks (#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
@kobayurii
Copy link
Member

#195

@kobayurii
Copy link
Member

kobayurii added a commit to kobayurii/nearcore that referenced this issue Mar 20, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
khorolets pushed a commit to near/nearcore that referenced this issue Apr 9, 2024
…ng Optimistic Blocks (#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue Apr 9, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue Apr 23, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
khorolets pushed a commit to near/nearcore that referenced this issue Apr 23, 2024
…ng Optimistic Blocks (#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 13, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 13, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 13, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 13, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 14, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 14, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 14, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
kobayurii added a commit to kobayurii/nearcore that referenced this issue May 14, 2024
…ng Optimistic Blocks (near#10692)

Hello everyone!

This pull request addresses two urgent tasks related to our project's
[Read RPC](https://github.com/near/read-rpc) functionality.

[Issue 1](near/read-rpc#188): 
Making our state-indexer compatible with the near-indexer to eliminate
the 3-second delay caused by
[Lake-framework](https://github.com/near/near-lake-framework-rs). This
compatibility enhancement ensures smoother and more efficient operation
of our system by removing unnecessary delays.

[Issue 2](near/read-rpc#186): 
Enhancing our service to handle requests for optimistic blocks directly,
without proxying to nodes. This optimization streamlines the process,
improving response times and overall system performance.

To achieve these tasks, modifications have been made to the
near-indexer. Specifically, the `build_streamer_message` method has been
made public to facilitate the creation of `StreamerMessage` for
optimistic blocks.

This pull request aims to enhance the reliability, efficiency, and
performance of our Read RPC functionality, addressing critical needs
within our project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request performance
Projects
None yet
Development

No branches or pull requests

2 participants