What have we learned from Graph-Powered Machine Learning so far?
Knowledge sharing has always been extremely important for Engineering at GraphAware.Whether it is techniques, tools or technology, lessons learned from our consulting engagements, or experience in general,sharing sparks conversation, creativity and discovery of different or better ways to do things.
Last week we at GraphAware hosted yet another webinar. This time we talked about Money Laundering and how Hume can help you detect money laundering activities. Don’t worry if you missed it; here is your summary of what we covered.
Welcome back to the Graph-Powered Machine Learning book club. As you know by now, Graph-Powered Machine Learning is a book written by our very own Dr. Alessandro Negro. The book is a must-read for all data scientists, but it’s also a great read for everyone interested in graphs. In this blog series, I summarise the key points of each chapter and provide some more explanations useful for us less technically savvy. We learned the basics about machine learning, graphs, and why the two are a great fit in the first chapter.
There are a multitude of databases to choose from when deciding how to store your data. They differ in complexity, scalability, data modelling possibilities they offer, and application. Let’s walk through some of the most popular databases and their differences.
Only a few things are more satisfying for a graph data scientist than playing with Neo4j Graph Data Science library algorithms, most probably running them in production and at scale. Possibly also using them to fight against scammers and fraudsters that every day threatens your business.
It is always a valuable opportunity to understand our product better and recognize user needs. At GraphAware, building Hume, a graph-powered insight engine, we are proud of making an impact on our customers’ success. However, we use Hume also to support our processes and help our own needs. In the case of the event that took place throughout December, we were also able to have great fun and integrate the team.
Last week, I had the pleasure of hosting a webinar with our Director of Product, Esther Bergmark, and our CTO, Christophe Willemsen. This webinar introduced our new release Hume 2.11, so we covered the most exciting features of the release, including no-code graph navigation, custom visibility of Actions in Perspectives, and Perspective API. The 2.11 version comes with more updates and advancements such as Configuration as Code and Polygons in Geospatial Analysis - about which you can read in our release blog.
We are proud to announce the 2.11 release of Hume. Advanced Expand is introduced to Hume with this release, which lets users create complex queries to navigate the graph without using Cypher. Additionally, the visibility of Actions can now be defined per Perspectives, enabling a tailored exploration experience; a GraphQL API exposes data from Perspectives so that other apps can leverage the power of Hume. And finally, Configuration-as-Code allows administrators to manage Hume configuration files in a repository.
About a year ago, I first logged into Hume - in the morning, I had started my new job at GraphAware, and a few hours later, I had a canvas in front of me with a few person nodes connected by relationships. Hume Visualisation. The graph: a murder mystery. Me: a newbie, never typed a line of code in any query language.