Apps, bots, data, cloud services—APIs enable connection and communication between numerous applications. They are the glue of digitalization and allow companies to assert themselves in their complex ecosystems. They guarantee smooth collaboration with business partners and customers.

Whether it's frontend with backend or different services with each other, the API concept should meet individual requirements and be standardized at the same time. This is how we guarantee tailor-made functions, such as filter options, rapid expansion through the addition of standardized services, and ease of understanding.

Step by step to success

We use APIs from others in almost every piece of software, develop our own APIs, or build API gateways for systems. API gateways allow connection to multiple APIs via a single endpoint. This means that individual old or non-standardized APIs can be gradually converted without jeopardizing ongoing operations.

Standardized and tested

When building and using APIs and API gateways, we rely on what has already been established: standardized protocols and tested technologies for optimum maintainability.

GraphQL excels as an API gateway, especially when upgrading legacy systems.

Schemas for GraphQL are descriptive and enable developers from different platforms to use a common language. Depending on the app and platform, one and the same endpoint can provide exactly the data and logic that is needed. This offers a whole host of advantages:

• Flexible structure

• Frontend builds the query as needed

• Resource-efficient: Only what is requested is sent

• Self-documenting

• Typed data

• Data-efficient: Only requested data fields are exchanged

• Authentication and authorization

For us, RESTful is the absolute standard in the field of APIs. It impresses with its simplicity and still has its raison d'être for certain use cases.

We also rely on serverless Lambda Function: This enables extremely affordable hosting, as only the actual computing time is charged.

User-friendly interface through API integration

The protocols and technologies we use have been generating enthusiasm among large companies for years. Uber, for example, integrates interfaces to Tripadvisor, payment service providers, and delivery services, enabling drivers and end users to access a wide range of services—all in a single interface.

Protocols & technologies

• RESTful

• GraphQL

• Node.js

• Lambda functions (serverless)
  

Databases are also important, no question about it

They form the heart of every application that cannot do without a persistence layer – and that is most applications.

There are fundamentally different approaches to the type of database. Relational databases, document-based databases, and graph databases are widely used. Which is the best option? Each type has its own advantages and disadvantages.

The right database in detail

Which type is suitable for your case depends very much on the application in question. Without a fixed data structure, document-based databases can be useful. If, on the other hand, you want to build a recommendation engine, it makes sense to use a graph database. Related entities are stored in a graph structure, which makes it relatively easy to read similar entities without having to implement a lot of your own logic.

The right database is always considered on a case-by-case basis: the requirements determine the right database. This avoids unnecessary effort due to features that you would have to implement yourself, which would already be taken care of by using the right database system.