Skip to content
This repository was archived by the owner on Feb 19, 2025. It is now read-only.

softfly/softfly-integration

Repository files navigation

Softfly Integration

Build Status Coverage Status Quality Gate Status
Services (beans) for repetitive and common functions of integration platforms.

Links:

https://softfly.github.io/softfly-integration/

Services (beans):

Objective

  • An ideally run project that can be used as a model for other projects.
    • Clean code.
    • Clean, short and concise documentation closely related and mapping specific areas of the code.
  • Comparison of different technologies for the same use cases.
  • Base code for articles.

Project plan

  • Design a skeleton of classes and interfaces that simulate happy flow in Java SE.
  • Add Spring Boot.
  • Add Spring Web Services.
  • Add JPA.
  • Add NoSQL.
  • Deploy in cloud providers e.g. AWS, OpenShift.
  • Add performance tests.
  • Add large file support by streaming.
  • Add JBPM.
  • Deploy on Aplication Server e.g. Wildfly.
  • Implement services.
  • Add integration test framework.
  • Add artificial intelligence to inference and adding business rules to services from integration testing.

Examples of projects

The example application that transmits an invoice from the seller to the buyer.

# Step Service
Receive the document from the endpoint. IncomingShipment
1 Recognize the document format. DocumentRecognizeFormat
2 Validate schema of the document. DocumentValidationSchema
3 (Optional) Transform to the supported document format by DocumentValidationBusiness. Transformation
4 Validate business validation of the document. DocumentValidationBusiness
5 Parse the document to POJO (recipients). Parser
... Other business steps. (Changes in the content of the document.)
6 Determine the shipment (endpoints, recipient) to which the document should be sent. OutgoingShipment
7 Generate the document from POJO. Transformation or Formatter
8 (Optional) Transform to the recipient's document format. Transformation
9 Send the document. SenderEndpoint

TODOs

  • Divide the project into microservices after the skeleton design phase. (Prototyping is faster on a single project.)

About

Services (beans) for repetitive and common functions of integration platforms.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •  

Languages