soa | 易学教程

Is it a good thing for a custom rest protocol to be binary based instead of text based like Http?

阅读更多关于 Is it a good thing for a custom rest protocol to be binary based instead of text based like Http?

问题 Have you ever seen a good reason to create a custom binary rest protocol instead of using the basic http rest implementation? I am currently working on a service oriented architecture framework in .Net responsible for hosting and consuming services. I don't want to be based on an existing framework like Remoting or WCF, because I want total flexibility and control for performing custom optimization. So here I am trying to find the best protocol for handling this SOA framework. I like the

使用WCF实现SOA面向服务编程—— 架构设计

阅读更多关于使用WCF实现SOA面向服务编程—— 架构设计

本文转载: http://kb.cnblogs.com/page/96479/ SOA本身就是一种面向企业级服务的系统架构，简单来说，SOA就是一种进行系统开发的新的体系架构，在基于SOA架构的系统中，具体应用程序的功能是由一些松耦合并且具有统一接口定义方式的组件（也就是service）组合构建起来的。因此，基于SOA的架构也一定是从企业的具体需求开始构建的。但是，SOA和其它企业架构的不同之处就在于SOA提供的业务灵活性。业务灵活性是指企业能对业务变更快速和有效地进行响应、并且利用业务变更来得到竞争优势的能力。对企业级架构设计师来说，创建一个业务灵活的架构意味着创建一个可以满足当前还未知的业务需求的IT架构。使用WCF实现SOA，正好可以利用 WCF的灵活性，把业务层封装，发布为Web服务。这样可以降低系统的耦合度，加大对未知业务的扩展性。　　Web服务本来就是没有区分代码的，在这个例子里在下多开发了一个Service Interface目的是为了使系统更易于管理。在开发期间，Service是不断更改的，如果在UI层上直接调用服务层，那更改将会是频密的，所以在这里在下开发一个Service Interface层目的是为了把WSDL集成在同一个DLL程序集里面，进行统一修改。最后UI层只要直接调用Service Interface，就可以对系统直接进行操作

How to restrict web service data contract properties based on user role

阅读更多关于 How to restrict web service data contract properties based on user role

问题 I have the following web service: [DataContract] public class Project { public long Id { get; set; } public string Name { get; set; } } [OperationContract] public Project GetProject(long Id); Now I want to add a SecretData property that should only be exposed to certain users. I've come up with several ideas, but none of them sit quite well with me: Add a nullable SecretData property to Project . If the user doesn't have permission to view it, set it to null . This seems like the simplest

RESTful JSON based SOA Registry

阅读更多关于 RESTful JSON based SOA Registry

问题 I'm searching for a simple registry which provides a very simple API and works with resources that can be described as JSON. I'm designing a Resource Oriented Architecture (entirely HTTP REST, no WS-*'s ESB or other things, all communications are made over network, are stateless and all services share nothing) that will be all talking using JSON as primary data, so I'm a bit bored to use XML only to work with that SOA Registry. Disclaimer: I really love WSO2 stuff, I learned SOA looking at

淘宝SOA框架dubbo学习（1）--first demo

阅读更多关于淘宝SOA框架dubbo学习（1）--first demo

部署开发，需要三部分：服务提供者、服务容器、服务消费者本人用 eclipse 开发 1、服务提供者jar生成 A、项目截图 B、源码： ? 1 2 3 4 5 package com.alibaba.dubbo.demo; public interface DemoService { String sayHello(String name); } ? 1 2 3 4 5 6 7 8 9 package com.alibaba.dubbo.demo.provider; import com.alibaba.dubbo.demo.DemoService; public class DemoServiceImpl implements DemoService{ public String sayHello(String name) { return "Hello " + name; } } provider.xml ? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 <? xml version = "1.0" encoding = "UTF-8" ?> < beans xmlns = "http://www.springframework.org/schema/beans" xmlns:xsi =

Generating monotonically increasing integers (max 64bit)

阅读更多关于 Generating monotonically increasing integers (max 64bit)

问题 As part of a new project we need a service which can generate monotonically increasing integers. Requirements for the service are: service does not need to produce contiguous integer as long as it produces monotonically increasing integers it should be fine It should produce 64 bit integer the service should be highly available services should be resilient to failure (or restarts) I was planing to use redis ( INCR ) as a back-end store with replication enable but the issue is if the master

What is the best practice to define method signature in Service oriented architecture for service call?

阅读更多关于 What is the best practice to define method signature in Service oriented architecture for service call?

问题 What is the best practice to define service call prototype/signature while developing application in service oriented architecture. For Example I want to create Service call to send email. Let say I have following object in my domain layer [datacontract] public class Email { public string To { get; set; } public string From { get; set; } public string Message { get; set; } public string Subject { get; set; } //I am not going to use this properties in send email method public string OtherProp1

So am I talking about a SOA here?

阅读更多关于 So am I talking about a SOA here?

问题 For a government contract we will be proposing to build a traffic monitoring architecture. We will have the following components: Video camera's set up around the area of interest. The cameras will be aware of their location and orientation and viewing parameters. A GIS map server which can be queried for streets, building, etc. An algorithm the takes in raw video and street location information and outputs car locations. Another algorithm takes in car locations and very low level street

interfaces integration between products

阅读更多关于 interfaces integration between products

问题 In my company we develop internal products and usually this products must be integrated (typical scenario). Our solution is always use SOA web services for this kind of task. This is a solution that forces different products to develop same UI interfaces, and the responsibility of this interfaces or process is sometimes not clear between our teams. I want to propose an alternative solution, I think that sometimes each product publish SOA web services but in addition publish web-pages, that

how to implement SOA in java?

阅读更多关于 how to implement SOA in java?

问题 I am new for SOA.i want to known how to implement SOA in Java.i am go through various sites that only deals with the concept,it don't give clear idea about the implementation details,for using SOA in Java.plz provide an details for how to implements SOA. Thanks 回答1: SOA is about design principles (some might even say it's a paradigm) and less about tools and implementation, so it is difficult to fire up your IDE and "implement an SOA". Because SOA is bigger and complexer than, say, a design