Biztalk vs. Data Layer APIs

My company is going to go through a large project, in which our client needs a large client portal with the introduction of cms, crm. This will require interacting with data from several sources within the framework of our clients' business, which include XML server backends, SQL databases, web services, etc.

Our proposed solution would be to write an API in C # to provide a common interface with all of these systems. It will be scalable for future and parallel projects within the company.

Our client expressed interest in using Biztalk, and not as a special API for this integration, because they believe that this is a corporate solution that any of their suppliers could get and use, and it will be better supported.

We believe that the configuration work using Biztalk would be quite difficult for all the business rules they needed, and the interface for the new application to get data from and from Biztalk should still be written.

Do we prefer the custom API above Biztalk? Could Biztalk be the right data layer to provide an interface for the new customer portal we are writing. We had no experience using Biztalk, so any input would be appreciated.

+3
source share
2 answers

, , . . , , - "" .

BizTalk . , " , ", " ".

BizTalk " " , // BizTalk " ". ( , ).

" ", , , " ". " " " ". , /bugfix. BizTalk - .

; "BizTalk, , ".

, ,

+3

BizTalk :

'

BizTalk . " " (, Request-Response, OneWay ..).

"" BizTalk ( , "Receive Port" + "Receive location" ). Orchestration ( -) SendPort ( โ†’ ) . ( , ).

BizTalk , "Publisher" "Subscriber" . , .

BizTalk - API- .Net , ", ".Net " BizTalk.

- ; ", , / BizTalk". BizTalk ; , .

+1

Source: https://habr.com/ru/post/1738023/


All Articles