-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Stabilize AWS Neptune module #6857
Comments
Sent a PR for adding Neptune constructs here: #12763 |
Can this be resolved now that L2 constructs are available for Neptune? |
@cornerwings we usually resolve these once the Construct Library is Generally Available (in other words, Stable). Since the Neptune L2 was merged very recently, it's still considered Experimental - as can be seen in its ReadMe: |
Ah I see, thanks for the clarification. |
I know #21972 is closed but I think it's worth revisiting as part of this stabilization |
Add your +1 👍 to help us prioritize high-level constructs for this service
Overview:
Amazon Neptune is a fast, reliable, fully managed graph database service that makes it easy to build and run applications that work with highly connected datasets. The core of Neptune is a purpose-built, high-performance graph database engine. This engine is optimized for storing billions of relationships and querying the graph with milliseconds latency. Neptune supports the popular graph query languages Apache TinkerPop Gremlin and W3C’s SPARQL, enabling you to build queries that efficiently navigate highly connected datasets. Neptune powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, and network security.
AWS Docs
Maturity: CloudFormation Resources Only
See the AWS Construct Library Module Lifecycle doc for more information about maturity levels.
Implementation:
See the CDK API Reference for more implementation details.
Issue list:
The text was updated successfully, but these errors were encountered: