search

antonovdmitriy / bridle

1 stars 0 forks source link
apache-camel docker-compose integration spring-boot test-containers

readme

Bridle

Codacy BadgeQuality Gate Status Reliability Rating Maintainability Rating Security Rating Technical Debt Coverage Code Smells Bugs Vulnerabilities Duplicated Lines (%)

Overview

Bridle is a convenient, configurable application designed for handling the most common integration tasks, built on the experience of using Apache Camel and Spring Boot.

Technology Stack

Why is this project needed?

Apache Camel offers many components and features for writing integration routes using enterprise integration patterns. According to the author's experience, it is possible to generalize typical integration scenarios and create a convenient tool for everyday use in projects where integration is needed.

The second reason for the project's creation is the author's dissatisfaction with the convenience of configuring Apache Camel components and endpoints. It is possible to configure a component via Spring auto-configurations, but they only work for one component of each type. The author has encountered many situations when it would be necessary to add a component or endpoint setting from the list of possible ones, but the configuration did not allow this without rebuilding the application.

The third reason is the creation of standard routes, which, if desired, can be copied to third-party projects and make custom changes for specific integration tasks. The current examples in the Apache Camel project do not, in the author's opinion, represent real examples typical of enterprise applications. The author attempts to account for the many mandatory components that are present in the actual project. (validation, logging, metrics, authentication, etc.)

Project Structure

(TBD)

Usage Examples

(TBD)