soa

问题 Currently I am creating a WCF service which has to connect to a DAL which, just connects to a database using ADO.net and stored procedures. The DAl writes its responses from the database to a datacontract which is passed over the wire to the client via the service. I was reading that this may possibly be the anti pattern 'CRudy Interface', but I wasn't sure as I am sharing the datacontract. If I am using an anti pattern, can anyone suggest a better pattern to use for the behavior I require?

问题 I'm an architect in a large scale financial company and we are in the beginning of implementing a new business oriented infosystem across our different countries. From the very early on the core idea has been to follow microservice oriented principles as much as possible (and making sure engineers have read Building Microservices book by Sam Newman) . By now I've come to crossroads. Our services are primarily JSON REST services using Swagger for automated documentation, but in order to use

问题 What is the path of least evil when dealing with polymorphism and inheritance of entity types in a service-oriented architecture? A principle of SOA (as I understand it) is to have entity classes as mere data constructs, lacking in any business logic. All business logic is contained in narrow-scoped, loosely-coupled services. This means service implementations are as small as possible furthering the loose coupling, and means the entities avoid having to know about every behaviour the system

问题 From past few months I am working on projects in latest dot net frameworks. I feel that in latest dot net versions "services" are encouraged over components. Is that correct? I have seen in silver light (I am a beginner in silver light) all the DB layer operations are exposed as services. I don't know right now component programs also are available? What is the advantages? What about the performance if all the layers are exposed as services instead of DLLS? Please through some light on this

问题 I want to use asymmetric encryption of headers in RESTful requests to verify the identity of the system sending the request: i e System A encrypts it's name, timestamp, and the service name using it's public key in a request to System B. System B then uses the public key of System A to decrypt, proving the authenticity of the request. 1) Does php-mcrypt support this? 2) Has anyone benchmarked this type of operation? 回答1: No, mcrypt is just symmetric block ciphers. However the PHP OpenSSL

问题 I want to use asymmetric encryption of headers in RESTful requests to verify the identity of the system sending the request: i e System A encrypts it's name, timestamp, and the service name using it's public key in a request to System B. System B then uses the public key of System A to decrypt, proving the authenticity of the request. 1) Does php-mcrypt support this? 2) Has anyone benchmarked this type of operation? 回答1: No, mcrypt is just symmetric block ciphers. However the PHP OpenSSL

问题 What is the proper way to handle polymorphic business objects in a WCF/SOAP world? It seems to me that SOA and OOP are at odds with each other - to expose a clean WSDL you need concrete objects, typically not even utilizing inheritance. On the other hand, presumably in the underlying system, you'll want to follow proper OO design. What do people typically do here? Build a set of WCF contract objects, forgoing OOP principles, then convert to and from another set of objects in the actual logic

问题 Lets assume that I'm dealing with a service that involves sending large amounts of data. If I implement this with WCF, will WCF throttle the service based on how much memory each request takes to serve? Or will I be getting continuous out of memory exceptions each time I receive a large number of hits to my service? I'm quite curious as to dealing with this problem outside of WCF, I'm still a bit new to service development... 回答1: While using the binding attributes and readerQuotas like

问题 We are about to begin architecting a service oriented framework (SOA) which will certainly involve a high number of of granular web services (REST in WCF). We've been quite disciplined in unit testing our client and server-side code base, however we don't have much of any experience in unit testing web services. We're really looking for guidance as to where the tests should be written and recommendations on what approach to use when unit testing our services. Should we write tests that make

问题 I am building a completely new system using WCF. I am going to use Contract-First Approach for a service which is to be built based on Service Oriented concepts. I have a service operation that returns a bank account details of a user. The account can be of type “FixedAccount” or “SavingsAccount”. I have designed the service as follows. [ServiceContract] interface IMyService { [OperationContract] AccountSummary AccountsForUser(User user); } [DataContract] class AccountSummary { [DataMember]