API endpoints for any type of Backend

The Frank!Framework is ideally suited to create (REST) API endpoints for any type of back-end. It offers a simple, manageable and maintainable way to build APIs. This way you can easily connect your new front-end to different types of databases and applications, but also to monolithic applications or a mainframe.

ESB messaging

The Frank!Framework makes translations between your applications and functions as an ESB. This makes it easier to connect new applications, or to replace an old application. The Frank!Framework also provides a message bus, message routing, standard components for data transformation, a management console and test tools.

The Frank!Framework can also be used for integration with an external ESB:

Central archiving solution (CMIS)

The Frank!Framework can be used as a solution to easily combine data from different archives. You can retrieve data, display it, modify it and send it back to the right place. This way you create a central point for managing and accessing multiple digital archives in a standardized way.

Migration solution

Imagine the Frank!Framework like a power strip. Migrating to a new application is as simple as plugging in a new plug. This way it’s easier to replace old applications. Your old application continues to run temporarily and the new application can be implemented gradually. This keeps your services uninterrupted during your digital transformation.

Api gateway functionality

A central place for requests to various microservices and APIs. The Frank!Framework provides secure APIs (authentication and authorization), scaling and message enrichment. An API gateway provides access to data from different applications and systems, and ensures standardized communication and management. Without the need for separate (custom) connections.

Translate services, e.g., Soap to Rest

Applications that communicate through SOAP do not interoperate with REST APIs. The Frank!Framework makes the translation between XML and JSON, allowing these types of services to work together. And everything remains insightful and manageable through the management console. In addition to REST and SOAP, the Frank!Framework has many out-of-the-box connectors for the most common standards such as SMTP, FTP, JMS and more!

Transactionality

Does your business process depend on correct handling of all steps/services? Then transactionality is essential. An example; in a financial process, party 3 may not be paid until party 1 and party 2 have both made payment. If something goes wrong anywhere in the process, you want all transactions to be automatically reversed.

Any programmer who has built transactionality into an application knows how challenging this is. The Frank!Framework provides support for transactionality; it’s just as simple as ticking or un-ticking a box and it’s done!

In addition, the Frank!Framework has extensive logging and testing tools for insight into each step and the ability to redo actions (resubmit).

(Batch) file transfer & handling

The Frank!Framework is suitable for secure and controlled transfer of large amounts of files from one place to another. The Frank!Framework also offers streaming capability, so that large (quantities of) files are sent with less prone to error.

Scheduling (triggers) & event driven automation

The Frank!Framework can execute actions based on various triggers and events. It is possible to kick off processes when adding a file to a folder, for example, or based on a simple cron job. This way, an administrator can automatically resend unprocessed messages, if your vendor’s API is temporarily unavailable. Of course, resending can also be done manually in the user-friendly Frank!Console.