aws-scala-sdk | It 's like the AWS SDK for Java | AWS library

by amazon-archives Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | aws-scala-sdk Summary

aws-scala-sdk is a Java library typically used in Cloud, AWS applications. aws-scala-sdk has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

It's like the AWS SDK for Java, but more Scala-y

Support

Quality

Security

License

Reuse

Support

aws-scala-sdk has a low active ecosystem.

It has 74 star(s) with 13 fork(s). There are 34 watchers for this library.

It had no major release in the last 6 months.

There are 7 open issues and 3 have been closed. On average issues are closed in 6 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of aws-scala-sdk is current.

Quality

aws-scala-sdk has 0 bugs and 0 code smells.

Security

aws-scala-sdk has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

aws-scala-sdk code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

aws-scala-sdk is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

aws-scala-sdk releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

aws-scala-sdk saves you 242 person hours of effort in developing the same functionality from scratch.

It has 589 lines of code, 35 functions and 13 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed aws-scala-sdk and discovered the below as its top functions. This is intended to give you an instant insight into aws-scala-sdk implemented functionality, and help decide if they suit your requirements.

Main entry point
Generates an Maven project
Gets the aggregator POM
Get the ftl template for the ftl client
Recursively delete a file
Creates a directory if it does not already exist
Returns the list of modules
Gets the name of the module
Generates client
Generates the client
Gets the Scala client

Get all kandi verified functions for this library.

aws-scala-sdk Key Features

No Key Features are available at this moment for aws-scala-sdk.

aws-scala-sdk Examples and Code Snippets

No Code Snippets are available at this moment for aws-scala-sdk.

Community Discussions

Trending Discussions on aws-scala-sdk

DynamoDB async access from Play Framework

QUESTION

DynamoDB async access from Play Framework

Asked 2017-Apr-25 at 09:21

I need to access and write to DynamoDB from a Play Framework application. There are already a couple of questions regarding this topic (here, here and here; however all of them are at least 3 years old).

The answer for the question is usually to use a wrapper (AWScala by seratch) or a library dedicated for Play:

However the wrapper simply calls the sync versions of the SDK underneath the hood. And if possible I would like to be able to update the AWS SDK as soon as a new version comes out and not be dependent on the used Scala/Play library to be updated first. So the best alternative for me turns out to be the aws-scala-sdk wrapper generator by awslabs. The async wrapper uses for example the Future putItemAsync(PutItemRequest putItemRequest, AsyncHandler asyncHandler) method which still returns a Java Future, but it's also possible to use the callbacks of the AsyncHandler to drive the response of a Scala Future:

...

ANSWER

Answered 2017-Apr-25 at 09:21

After spending a lot of time doing stress tests my doubts about using DynamoDB with Play I am fairly optimistic to use com.amazonaws.handlers.AsyncHandler.

Test setup: one server instance (type varying) with a couple of dedicated requester instances (m4.large). Each request contains a JSON payload which is written into the DynamoDB (about 200 Bytes). Each requester instance starts several threads which handle the actual requests. The requests are spread evenly over a period of time and each requester instance ramps its threads up in a staggered manner so that no requests are throttled by DynamoDB (table with 10000 provisioned write capacity units, no requests were ever throttled according to CloudWatch). The ulimit -n (number of open files) was increased to 20000 on the server instance because otherwise the server would behave weird (process didn't listen on port 9000 anymore, but some threads were still able to dispatch requests while others were not) above about 3500-4000 requester threads. Max Java heap size was 8GB.

My findings are as follows:

m4.large server instance: Below 2500-2700 requests/s response times are <60ms on average. Write throughput caps out at about 3700-3800 requests/s. Bottleneck is CPU, load constantly at 100%.
m4.4xlarge server instance: No matter how many request threads, response times constantly <50ms, average at about 10ms or lower. I was able to max out the 10000 provisioned write capacity units...

Source https://stackoverflow.com/questions/43406354

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install aws-scala-sdk

You can download it from GitHub.
You can use aws-scala-sdk like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the aws-scala-sdk component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .