(Translation) Software Architecture Style

Software Architecture Style

Kalyan bandarupalli, hystar Translation

Architectural style is a set of principles. You can use it to build a typical system architecture style in a specific field. The ability to implement a software architecture style depends on the ability and fundamental constraints of your organization to implement the architecture style. HereArticleExplains the architectural style to be selected based on a requirement.

 

Introduction

Architectural style is a set of principles. You can use it to build a typical system architecture style in a specific field. The ability to implement a software architecture style depends on the ability and fundamental constraints of your organization to implement the architecture style. This article explains what kind of architecture style should be selected based on a requirement.

 

Architecture Style

A typical practice is to combine multiple styles to define a complete architecture. For example, a layered architecture can be used with components-based, object-oriented, SOA, and other styles.

The following is a list of commonly used Software Architecture styles.

 

Client/Server

Use this style when the following conditions exist:

• This application is server-based and must support multiple clients.
• You are building a web-based application open through a browser
• You want to centralize data storage, backup, and management functions.

 

Component-based

When you consider using a component-based architecture

• Your application has special requirements that do not include ui or business processing.
• The stored procedure that your application executes is a function that has little or no input.
• You need to create a pluggable architecture that allows you to update or replace individual components.

 

Layered

You can consider using a layered architecture in the following situations:

• Your application is complex.
• You want to improve the maintainability and scalability of applications.
• Your application supports different types of clients and devices.

 

Message Bus

Use this style when the following conditions exist:

• Your existingProgramInteract with other programs to complete some tasks.
• You are implementing an application that requires interaction with external applications.
• You are implementing a publisher/subscriber Application

 

MVC Architecture Style

Consider the MVC style when the following situations exist:

• You want to improve the testability of the UI and make UI maintenance easier.
• You want to process the UI elements and UICodePhase Separation
• Your UI processing code does not implement any business logic.

 

SOA

Consider the service-oriented architecture in the following situations:

• You want to consume a service exposed by a third party.
• You want to build an application and combine a series of different services into a single UI.
• You need to create an SaaS (software as a service) application.
• You need to expose the service through a discoverable directory.

 

I am not easy to learn, and translation errors are inevitable. Please kindly advise me.