Patterns and Antipatterns

Patterns and Antipatterns¶

Patterns¶

Antipatterns¶

1. Direct SQL Connection

Don't connect to another systems database — this also applies if that application is your application. It might not always be your application and may eventually find its way to a different team. Doing this also does not respect that systems' load. Below are variations of the the SQL database connections from bad to ideal.

Bad SQL Connection¶

Acceptable SQL Connection¶

Ideal SQL Connection¶

While the image doesn't show this, the call is happening over an APIM

1. Polling

Don't use polling if you can avoid it. This is a perfect example to favor event driven architecture.

1. SFTP Usage

Avoid using this for standard internal data sharing, unless there is no alternatives.

1. Batching or Bulk Processing

A file based bulk process to systems that UL Solutions does not have control over, often, cannot be avoided. However, for systems built internally, there are alternatives to taking this approach. Instead of having the source submit a large amount of data to a shared location (SFTP), it may be easier (and more effective) to have the target system provide an endpoint that can take one or more records to process — ensure to have communicated the proper error handling. Does one failure mean all fail? Do you respond stating only one failed?