It’s official: AWS has a production-ready graph database. What features are included today, and what will be included in the near future, what use cases are targeted, and what does AWS Neptune’s release mean for users and graph database vendors?

AWS Neptune was sharp in its appointment with general availability (GA). While speculation was haywire, AWS sources were very specific about Neptune going GA in late May. So, now that it’s here, how much impact will Neptune have for users, and will it ‘Amazon‘ the graph database landscape?

Even before the announcement, AWS emphasized two key points: Neptune would enable users to seamlessly go from proof of concept to production, and there was great interest by many major clients. Its people were confident about the GA timeplan and how AWS clients using Neptune pre-GA would be able to go to production upon GA.

The names included in yesterday’s press release do not disappoint: Samsung Electronics, Pearson, Intuit, Siemens, AstraZeneca, FINRA, LifeOmic, Blackfynn, and Amazon Alexa. Their use cases range from fraud detection to medical research, and AWS says that was precisely what drove Neptune’s development and is reflected in Neptune’s profile.

Neptune has a dual nature, as it supports both prevalent graph database models, RDF, and Property Graphs (PG). AWS says they wanted to give customers choice, and adds that “which model should I use” was a common question among early adopters.

Read the full article on ZDNet