DEV Community: LFC

Quick approach: Anti-corruption layer pattern

LFC — Wed, 24 Aug 2022 21:02:00 +0000

The anti-corruption layer pattern implements a facade or adapter between different systems with different semantics. The main purpose is to translate the request from one system to another, trying to reduce dependencies and limitations.

"Create an isolating layer to provide clients with functionality in terms of their own domain model. The layer talks to the other system through its existing interface, requiring little or no modification to the other system. Internally the layer translates in both directions as necessary between the two models"
Eric Evans’s Domain Driven Design book

Context

Several companies dedicate their efforts to solving specific problems under specific mechanisms, technologies and architectures, forgetting a potential unification or communication of those systems in the future.

Many of these scenarios are present when trying to interface a new or recent system with legacy components, causing compatibility issues. In these cases, the priority must be to respect the restrictions of the system and not include bad practices in our code in order to force communication between those involved.

An ally to solve this problem is to implement an anti-corruption layer, which serves as an adapter and translator between the requests that the systems or subsystems involved make.

When to use?

If you do not have homogeneous systems, you can use this pattern in order to avoid mixing protocols and communication mechanisms between different architectures and subsystems.

Advantages

A standard interface to expose functionality.
Evolve implementations without sacrificing compatibility or efficiency.
Discovering services may be easier through a middle layer.
Centralized error handling in the middle layer.
Move and unify communication, monitoring, security, and interoperability responsibilities to a layer that does not interfere with legacy or new systems.

Clarity and Communication, fundamental techniques in Software Architecture

LFC — Mon, 11 May 2020 05:32:36 +0000

Technical decisions, project goals, specifications, and restrictions frequently are communicated in large Microsoft Word documents, extensive paragraphs, and many tables with change control.

I regard it is not the best approach to share knowledge, decisions, and establish a convenient work environment around a project and their members, I have two reasons that support my thoughts:

No one on your team is going to read and memorize a 50-page architecture document.
We are living in an environment that demands cross participation or cooperation instead of accepting a lot of instructions ruled by the architects or technical leaders.

According to that, I recommend a few ideas to be agile, have effective communication, leadership, and simplicity in complex scenarios.

Tools to transmit thoughts
Use diagram modelers in order to communicate your ideas and workflows. Often this method promotes a better scope understanding and allows identifying several restrictions at first sight.
Options: Visio or Enterprise Architect, and so forth.

Post-it notes or whiteboarding
Architects, leaders, developers into a room in order to draw, divulge, and share technical considerations. At the end of the session, you could want to snap some pictures and share them with the team in order to provide valuable stuff for reviews or future discussions.

Expose details about architectural decisions
After taking all the conclusions, concerns, concepts, or opinions, it is time to expose the framework or approach, involve the technical people in the architecture process, and validate if we are in a good shape regarding the needs of the project. A collaborative environment will improve communication inside the team.

Repeat the process. Architectures do not have to be rigid.

Clarity and Communication, fundamental techniques in Software Architecture

Luis Chavarriaga ・ May 10, 2020 ・ 2 min read
Medium

Query to get Primary Key & Foreign Key columns

LFC — Tue, 24 Sep 2019 19:42:28 +0000

I want to share this query for SQL Server to get PK, FK, and Data Type information from a DB Table.

Enjoy!

My TOP resources for .NET & Azure

LFC — Thu, 29 Aug 2019 16:48:40 +0000

This time, I am going to share my TOP resources about .NET and Azure

General

Microsoft Docs
https://docs.microsoft.com/en-us/

Microsoft Learn
https://docs.microsoft.com/en-us/learn/

.NET Architecture Guides
https://dotnet.microsoft.com/learn/dotnet/architecture-guides

Browse code samples
Get started with Microsoft developer tools and technologies
https://docs.microsoft.com/en-us/samples/browse/

Azure

Azure Architecture Center
https://docs.microsoft.com/en-us/azure/architecture/

Azure Application Architecture Guide
https://docs.microsoft.com/en-us/azure/architecture/guide/

Cloud Design Patterns
https://docs.microsoft.com/en-us/azure/architecture/patterns/

Azure Reference Architectures
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/

Azure Solutions Architectures
https://azure.microsoft.com/en-us/solutions/architecture/

Get Started with CosmosDB
https://www.gotcosmos.com

Bonus

A collection of simple recommendations for decent Web application frontends
https://roca-style.org

Semantic Versioning 2.0.0
https://semver.org/#semantic-versioning-200

HTTP Status Codes
https://httpstatuses.com/

How to move a Blob to another Container

LFC — Mon, 19 Aug 2019 23:33:23 +0000

In this post, I am going to share a method that moves a blob to another container.

This content applies for:

Azure Storage Accounts.
.NET Core 2.2.
Different containers on the same storage account.

Steps

I have a CloudStorageAccount object that represents the Azure Storage Account.
I have a CloudBlobClient object that represents a Blob service.
In the constructor, CloudStorageAccount and CloudBlobClient are initialized.
MoveBlob method creates a reference of source container and destination container using GetContainerReference method of CloudBlobClient object.
I get a blob reference using GetBlockBlobReference method using the previous containers references.
Finally, I invoke StartCopyAsync method in order to copy the blob to another container, then, the source blob is deleted.

Tip for Preventing XSS in ASP.NET

LFC — Sat, 10 Aug 2019 18:43:04 +0000

I am going to show you an old but useful tip in order to prevent command injection in our forms.

First of all, We have this line that does not encode HTML:

In order to encode correctly this output and avoid XSS attacks, you should convert it to this way:

However, ASP.NET MVC introduces this reduced syntax with the same purpose:

Did you see it?
The key is to replace <%= with <%:

Happy coding!

DEV Community: LFC

Quick approach: Anti-corruption layer pattern

Clarity and Communication, fundamental techniques in Software Architecture

Clarity and Communication, fundamental techniques in Software Architecture

Luis Chavarriaga ・ May 10, 2020 ・ 2 min read Medium

Query to get Primary Key & Foreign Key columns

My TOP resources for .NET & Azure

How to move a Blob to another Container

Tip for Preventing XSS in ASP.NET

Luis Chavarriaga ・ May 10, 2020 ・ 2 min read
Medium