soa

Difference between SOA and ESB

让人想犯罪 __ 提交于 2020-01-28 16:24:07
问题 I am confused in these web service terminologies SOA, ESB. Anybody please explain. 回答1: SOA is an architectural approach where you expose and encapsulate 'services' in a coarse-grained manner. It does not prescribe any technical mechanism or implementation. SOA is more related to boundary / integration interaction between systems. So if system A exposes services using a SOA I can interact with those services from system B. An ESB on the other hand is a technical implementation that aids in

SOA/WCF dissecting the system & service boundaries

让人想犯罪 __ 提交于 2020-01-16 21:40:32
问题 I'm building a system which will have a few channels feeding different clients (MonoDroid, MonoTouch, Asp.Net Mvc, REST API) I'm trying to adopt an SOA archetecture and also trying to adopt the persistence by reachability pattern (http://www.udidahan.com/2009/06/29/dont-create-aggregate-roots/) My question relates to the design of the archetecture. How best to split the system into discreet chunks to benefit from SOA. In my model have a SystemImplementation which represents the an

SOA/WCF dissecting the system & service boundaries

拟墨画扇 提交于 2020-01-16 21:37:13
问题 I'm building a system which will have a few channels feeding different clients (MonoDroid, MonoTouch, Asp.Net Mvc, REST API) I'm trying to adopt an SOA archetecture and also trying to adopt the persistence by reachability pattern (http://www.udidahan.com/2009/06/29/dont-create-aggregate-roots/) My question relates to the design of the archetecture. How best to split the system into discreet chunks to benefit from SOA. In my model have a SystemImplementation which represents the an

SOA/WCF dissecting the system & service boundaries

拟墨画扇 提交于 2020-01-16 21:35:07
问题 I'm building a system which will have a few channels feeding different clients (MonoDroid, MonoTouch, Asp.Net Mvc, REST API) I'm trying to adopt an SOA archetecture and also trying to adopt the persistence by reachability pattern (http://www.udidahan.com/2009/06/29/dont-create-aggregate-roots/) My question relates to the design of the archetecture. How best to split the system into discreet chunks to benefit from SOA. In my model have a SystemImplementation which represents the an

soa bofu 面向企业的信息化战略

拜拜、爱过 提交于 2020-01-16 11:28:47
从soa谈起,现在soa很多年了,但这个概念并不过时,反而成为重要的it基础 ddd 领域模型驱动,其实不用这个概念也行,就叫,业务功能模型吧,应该参考微服务的思想,面向企业的知识与资源。 面向业务的功能单元 Business-oriented functional units 这是我提出的概念叫 BOFU 所以我就不用ddd了 小写 bofu具体 的说 bofu就是一个个 数据模型+相关的逻辑(规则,状态,关系,描述...) 一般由一种代码承载,使用纯净的代码这里 我选择并推荐的是 C# .net core standard 2.1 的类库来承载,尽量做到不受各种技术的污染,让业务代码保持最大限度 的纯净,这些业务数据模型+业务逻辑,由抽象层进行边界封装,以确保业务逻辑描述 的必要完备性。 bofu是面向企业,面向公司的,而非面向应用,它不属于任何一个应用程序 ,一个项目,在bofu的上一层是 soa。 soa是与技术相关的,要考虑公司自己硬件资源 所采用的一种,技术集合用于实现 让资源 (硬件)最优化,并且承载了bofu 或其中的一部分,以服务接口的姿态 向外授权开放服务层,在soa的上层 是应用壳,应用壳 可以是web pc站点,手机站点, 手机原生应用其它智能设备的站点或原生应用程pc端的桌面应用序 等的一种应用。一个公司根据 自己的需要 可以做很多应用, 从大层面

DNS(bind)服务器安装和配置

谁都会走 提交于 2020-01-16 03:13:36
一、前言 DNS 域名系统 (英文: D omain N ame S ystem,缩写: DNS )是因特网的一项服务。它作为将域名和IP地址相互映射的一个分布式数据库,能够使人更方便地访问互联网。DNS使用TCP和UDP端口53(TCP 53端口用于dns服务器自己同步数据,UDP 53端口用于查询解析)。是一个域名服务,应用层协议。 DNS查询原理及名词解释: dns查询:迭代查询、递归查询 如下图,从客户端到本地DNS服务器是属于递归查询,而DNS服务器之间的交互查询就是迭代查询。 总结: 1.递归查询: 一般客户机和服务器之间属递归查询,即当客户机向DNS服务器发出请求后,若DNS服务器本身不能解析,则会向另外的DNS服务器发出查询请求,得到结果后转交给客户机; 2.迭代查询(反复查询): 一般DNS服务器之间属迭代查询,如:若DNS2不能响应DNS1的请求,则它会将DNS3的IP给DNS2,以便其再向DNS3发出请求; 所谓递归查询就是:如果主机所询问的本地域名服务器不知道被查询的域名的IP地址,那么本地域名服务器就以DNS客户的身份,向其它根域名服务器继续发出查询请求报文(即替主机继续查询)” 也就是递归就是交给下一个服务器解决(下一个就相当于客户了,所以他也可以选择去递归,或者迭代)(迭代就是返回给当前的,当前自己再去处理) 递归即递给服务器,所有操作都有服务器来完成

How does SOA service discovery (UDDI) work in practice?

早过忘川 提交于 2020-01-12 16:35:34
问题 I'm just reading up on SOA and the service registry / UDDI get mentioned regularly. It sounds nice but how is used in reality? Is the registry meant to decouple a logical service from its' physical implementation (port, url etc)? Is the registry meant to be browsed by a human looking for an interesting service to play with? Would it be 'wrong' to hard-wire an application to the services it uses? 回答1: I find it to be more theoretically useful than practically useful. It is infrequently

ORM and SOA in the .NET world

爷,独闯天下 提交于 2020-01-12 07:10:59
问题 From my experience the major ORM frameworks for .NET (NHibernate, LinqToSql, Entity Framework) work best when they keep track of loaded objects. This works fine for simple client-server applications, but when using three- or more tier architecture with Web Services in a Service Oriented Archtitecture, this is not possible. Eventually, by writing a lot of code to do the tracking yourself it could be done, but isn't ORM supposed to simplify DB access? Is the idea to use ORM in service oriented

ORM and SOA in the .NET world

可紊 提交于 2020-01-12 07:09:27
问题 From my experience the major ORM frameworks for .NET (NHibernate, LinqToSql, Entity Framework) work best when they keep track of loaded objects. This works fine for simple client-server applications, but when using three- or more tier architecture with Web Services in a Service Oriented Archtitecture, this is not possible. Eventually, by writing a lot of code to do the tracking yourself it could be done, but isn't ORM supposed to simplify DB access? Is the idea to use ORM in service oriented

How to Implement Loose Coupling with a SOA Architecture

隐身守侯 提交于 2020-01-12 02:20:12
问题 I've been doing a lot of research lately about SOA and ESB's etc. I'm working on redesigning some legacy systems at work now and would like to build it with more of a SOA architecture than it currently has. We use these services in about 5 of our websites and one of the biggest problems we have right now with our legacy system is that almost all the time when we make bug fixes or updates we need to re-deploy our 5 websites which can be a quite time consuming process. My goal is to make the