Building APIs is not without challenges. While APIs can be considered strictly technical assets, the best APIs are often built by multidisciplinary teams because there are just so many things to think about. In this blog, I’ll share some simple rules to get you started.
With the introduction of new generation privacy and data protection laws, including our GDPR, the need for personal data classification towards compliancy is an absolute must. The requirement to be proactive is not only a feature of the GDPR, it can also be found in other privacy frameworks around the world like CPBR for all APEC countries. Thus, we have our newly introduced information classification policy, privacy classification policy, but how do we put those into practice?
Recently we started a project where the customer asked us to set up and manage a software selection process. The new software would replace the existing, outdated and lacking solution. One of the challenges involved in the assignment was that we needed to be open to both commercial off-the-shelf products and custom-made solutions. Since the solution was part of their business-critical systems, simply browsing the internet and trying a few demos would not suffice.
In this blog post I will explain how we managed the selection process.
End of last year, we thought it would be a good time for all our consultants in the integration unit to get some more insights in the key concepts of API management and to get some really hands-on experience with a variety of software from different vendors, and have some fun while we’re at it. What better way to do that than to organize our own API management hackathon!
When modelling information, it is important to balance easy to understand high level overviews with accurate and detailed models. In the beginning of a project, all there is are high-level overviews. Often they are not yet complete, and they are not very useful once you get into the details.
In this blog post I want to highlight a very simple yet powerful integration pattern: the notification pattern. The reason why it's not often used is because it does not map requirements one-to-one (and let’s be honest, it's also more complex than a simple point-to-point connection).