Artikel
How a technical tool can bring value, effectiveness and efficiency in your day-to-day business
If you own, or work for, a company that relies on data for their success, you understand the challenge of making sense of it all. Translating data into concrete decisions and next steps that help you grow or improve your business is difficult. Because what do you do when your data pool is actually an almost infinite amount of detailed information, constantly expanding, unstructured and disconnected?
A while ago we started working with Ravlling, a startup in travel with exactly this problem. They realised that though the search for a next travel destination should reflect the fun of the travelling itself, it can actually become a complex, demotivating and time consuming job, because:
Our client Ravlling made it their mission to solve this travel search paradox and aims to regain the trust of the traveller when looking for their next destination. To help accommodate them in the process of searching, browsing and navigating through (a huge amount of) European destinations and help them decide where to go, what to do, where to stay and how to get there.
A big challenge was to pick the right technology that could not only handle this amount of data, but also handle a large amount of different connections that are necessary to build a full travel journey structure. In the end the sky's the limit when it comes to travel, there are so many destinations, travel options, activities and so on to choose from. We needed to gather, connect and structure the data in the way that their customer would really be catered to their needs.
When researching technological options in our Discover & Strategise phase we came across many ways to handle the vast amount of data needed to solve the travel paradox. In this article we want to focus on two of these options:
This method is mostly chosen for applications with well-defined and stable data structures.
In the case of Ravlling their platform would be set up as a big catalogue of trips, something similar to a travel planner. Each trip would be like a page in the catalogue and each piece of information about the trip, like the destination, dates, and price, would be neatly organised into columns. It's like having a catalogue where you can easily look up specific trips based on criteria like the location or date. Though sufficient in some cases, for Ravlling, where there is a large amount of data and connections, constantly expanding, this form would be too rigid to move forward with.
This method works well in scenarios where flexibility, scalability and handling diverse data types are crucial.
Instead of a rigid catalogue, a graph database is more like a huge mapped wall of sticky notes. Each sticky note represents a location, and they are connected by lines that show how they're related. Each location is a point on the map, such as cities, airports, hotels, and activities. You can see how these points are connected and you can plan your trip accordingly. Whether you start with the destination, the type of transportation or your budget, you are always able to see and understand the connections. And whenever new locations come in, new connections are easily made.
For Ravlling this type of setup would be more fitting for the complexity of their data.
We’ve established that a graph database is the best choice when your data is all about relationships and connections, and you need to explore, understand and identify those connections in a smart and efficient way. By representing data as nodes and relationships, graph databases allow for efficient storage and quick retrieval of complex interconnected information. These can lead to a more effective decision-making process, enable better customer experience and in the end lead to increased profits.
As a digital agency we have seen that a graph database is beneficial for all major stakeholders in the development process:
"Graph databases serve as a technical tool that empowers businesses to ride the data waves"
So let’s make it a bit more concrete. We know the benefits of a graph database, but when should you consider a graph database specifically?
The use of graph databases can significantly enhance the value, efficiency, and effectiveness of day-to-day business operations, benefiting various stakeholders in the process. It has helped Ravlling in their first steps to solve the travel paradox, giving them control throughout their data, understanding their customers better through valuable insights, ultimately leading to increased profitability and customer satisfaction.
In essence, graph databases serve as a technical tool that empowers businesses and if you have a platform or service reliant on a large amount of data and connections that needs to work for you, your team and your end-users, we recommend you start exploring it today.
Ride the data wave with us. We’ll keep you afloat ;-)