You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project aims to implement a Ballerina connector for the AWS Redshift Data API using the AWS Redshift Java SDK. RedshiftDataClient will be wrapped using Ballerina's interop features, exposing Redshift operations as user-friendly Ballerina APIs.
Key features will include:
Executing SQL statements on Redshift.
Managing query results.
This connector will simplify Redshift interaction for Ballerina developers while ensuring performance and reliability.
Version
No response
The text was updated successfully, but these errors were encountered:
chathushkaayash
changed the title
Design and implement Ballerina AWS Redshift Data Api Connector
Design and implement Ballerina AWS Redshift Data API Connector
Dec 2, 2024
The Java SDK for the Redshift Data API provides both synchronous and asynchronous clients.
The synchronous client (RedshiftDataClient) offers a blocking approach, suitable for applications where calls need to execute sequentially and the thread can be blocked during API operations.
The asynchronous client (RedshiftDataAsyncClient) enables non-blocking operations, leveraging CompletableFuture to handle API calls. This is ideal for high-throughput or event-driven applications where non-blocking operations improve scalability.
Key Differences Between Sync and Async Clients
Execution Model:
Sync Client: Blocking calls, easier to use in straightforward applications.
Async Client: Non-blocking, better for use cases requiring parallel or background processing.
Performance:
I used Java Microbenchmark Harness (JMH) to compare the performance of the synchronous and asynchronous clients.
Interestingly, I found no significant performance difference between the two clients under my benchmark conditions. Both clients exhibited similar throughput, even in high-concurrency scenarios, suggesting that the choice between sync and async clients may depend more on the application's design requirements rather than raw performance.
Description
Ballerina AWS Redshift Data API Connector
This project aims to implement a Ballerina connector for the AWS Redshift Data API using the AWS Redshift Java SDK.
RedshiftDataClient
will be wrapped using Ballerina's interop features, exposing Redshift operations as user-friendly Ballerina APIs.Key features will include:
This connector will simplify Redshift interaction for Ballerina developers while ensuring performance and reliability.
Version
No response
The text was updated successfully, but these errors were encountered: