Is the application fully SOA?

Is it possible to build a large application entirely based on SOA? Or just a few servings? Registration of user accounts, accounting, mapping gis, sale, etc.?

In other words, would it be wise to build a GUI for such an application in HTML and Javascript that does everything that it exchanges via ajax for .NET .NET services on an internal server?

I do not see this losing all the functions of .net.aspx, such as form authentication, view state, etc. But my colleague says that if we are going to go for SOA, there is no need for .NET at the front end. But I think there should be some balance. Where do you draw the line? Should all database calls go through web services?

+3
source share
4 answers

I quote the words of the song β€œIf I Had a Hammer”. SOA is an architectural approach for developing software as a set of services. In my opinion, this is best for systems that have less direct delay and limited bandwidth, as well as high access costs, etc. (All of them are obviously very subjective). You do not need a complete SOA, just get a free connection between the components, which, in my opinion, are a good goal to achieve.

, , ADO.NET, , . . SOA , . ? ? , (, , , , -, ).

- . , SOA. DDD, , , , . , , , .

.

SO question

+1

, " SOA , ".

, , , - , SOA.

, , , , .

SOA , SOA.


EDIT:

. SOA .

+2

- , .

- ; , .

, , , , - ( ). - , concurrency. - , , .

( -), ASP.Net. , -.

, , , - IMO. MVC 2, . , (, jQuery, ).

, - . , AJAX/SOA, , . , ASP.Net .

+1

- back-end SOA. . .NET , , , , . , - , - .NET, Java ..

SOA , , XSLT , .

, , . SOA , . , SOA-, . - ​​ SOA. , , X, Y Z, SOA .

0

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


All Articles