soa

Differences between SCA (Service Component Architecture ) and ESB (Enterprise Service Bus)?

梦想的初衷 提交于 2019-12-10 21:43:39
问题 i have started learning about Software architectures and i came across these terms ESB and SCA . Now these terms i found quite confusing as they seems to serve the same purpose (i know this could sound ridiculous to people masters in these topics, still). Can anybody please explain the differences ? Any help appreciated. 回答1: Actually they are quite different from each other. ESB stands for Enterprise Service Bus. It is a pattern for how to decouple services that you use across your

什么是SOA,什么是SCA,什么是微服务?

梦想与她 提交于 2019-12-10 21:25:43
这里是修真院后端小课堂,每篇分享文从 【背景介绍】【知识剖析】【常见问题】【解决方案】【编码实战】【扩展思考】【更多讨论】【参考文献】 八个方面深度解析后端知识/技能。 大家好,我是IT修真院上海分院朱明星,一枚正直纯洁善良的JAVA程序员。 今天给大家分享一下,修真院官网任务九,深度思考中的知识点——什么是SOA,什么是SCA,什么是微服务? (1)背景介绍: 架构演变 单一应用架构 * 当网站流量很小时,只需一个应用,将所有功能都部署在一起,以减少部署节点和成本。 * 此时,用于简化增删改查工作量的数据访问框架(ORM) 是关键。 * 代码层面没有拆分,所有的业务逻辑都在一个项目里打包成一个二进制的编译后文件,通过这个文件进行部署,并提供业务能力。 垂直应用架构 * 当访问量逐渐增大,单一应用增加机器带来的加速度越来越小,将应用拆成互不相干的几个应用,以提升效率。 * 此时,用于加速前端页面开发的 Web框架(MVC) 是关键。 * 整个系统由多个模块组成,每个模块又由这种不同的部分组成。这样一来,我们就把整个系统拆解成了很多粒度较小的零件。 分布式服务架构 * 当垂直应用越来越多,应用之间交互不可避免,将核心业务抽取出来,作为独立的服务,逐渐形成稳定的服务中心,使前端应用能更快速的响应多变的市场需求。 * 此时,用于提高业务复用及整合的分布式服务框架(RPC) 是关键。

Getting JSON out put from restful java client

半世苍凉 提交于 2019-12-10 18:40:23
问题 I'm developing a web service using REST (Jersey 1.8). Currently I'm using XML to communicate between the Java client and the server. I need to change it to JSON: how can I do that? I have bunch of auto generated code from NetBeans, and have no idea what to do and how. When the testing the service it shows the JSON data. What I'm unable to do is deal with it within my main method. these are the tutorial I followed http://www.oracle.com/webfolder/technetwork/tutorials/obe/java

Twitter-Finagle使用ZK作为service discovery

萝らか妹 提交于 2019-12-10 06:11:52
http://blog.oskarsson.nu/post/40196324612/the-twitter-stack 需要翻墙! 中文版: http://www.csdn.net/article/2012-02-14/311806 http://www.javaflush.com/twitter%E7%9A%84%E5%BC%80%E6%BA%90rpc%E6%A1%86%E6%9E%B6finagle%E8%B5%84%E6%96%99%E6%95%B4%E7%90%86%E5%92%8C%E4%BB%8B%E7%BB%8D%E6%AF%94%E8%BE%83/ 来源: oschina 链接: https://my.oschina.net/u/1382024/blog/687267

Business logic in Camel processors vs service endpoints

瘦欲@ 提交于 2019-12-10 03:48:55
问题 In a Camel route, should I be thinking about putting my business logic in a discretely hosted bean endpoint, like a message-driven bean or a web service, vs just implementing it in Camel processors? It seems like cleaner separation of concerns to use Camel just for mediation & orchestration, using Processors as filters, rather than as a container for business logic. However I don't forsee the need for an EJB container at this time, and it seems like I'd need one to host MDBs. So cleaner

Designing services and operations in WCF

拟墨画扇 提交于 2019-12-09 23:56:01
问题 I would appreciate some guidance on modelling services and operations in WCF. I have a series of business domains, each with bespoke methods that I want to able to use over WCF. I guess an OO view would be something like: interface IBusinessDomain1 { MyClass1 Method1(...) MyClass2 Method2(...) } interface IBusinessDomain2 { MyClass3 Method3(...) MyClass4 Method4(...) } My natural inclination was to make each interface a service and each method an operation, the problem I have with this is

How To Implement Multi Layered Architecture in PHP

此生再无相见时 提交于 2019-12-09 18:10:30
问题 I have identified below layers to be implemented in my application. According to my knowledge multi layered architecture is prefered for an enterprise application. Presentation Layer Business Layer Data Access Layer Service Layer I have chosen Symfony2 as the framework to be used in the app. Symfony2 has MVC architecture built into it. And the above layers exist as below. Presentation Layer => Controller & Views Business Layer, Service Layer => Model Data Access Layer => Also Model but

Microservice vs SOA differs

老子叫甜甜 提交于 2019-12-09 17:03:06
问题 I was looking for differences b/w SOA and Microservices architecture style and found a good link https://www.infoq.com/articles/boot-microservices It Says: As a successor to "Service Oriented Architecture" (SOA), microservices can be categorized in the same family of "distributed systems", and carry forward many of the same concepts and practices of SOA. Where they differ, however, is in terms of the scope of responsibility given to an individual service. In SOA, a service may be responsible

SOA and WCF design questions: Is this an unusual system design?

百般思念 提交于 2019-12-09 12:29:43
问题 I have found myself responsible for carrying on the development of a system which I did not originally design and can't ask the original designers why certain design decisions were taken, as they are no longer here. I am a junior developer on design issues so didn't really know what to ask when I started on the project which was my first SOA / WCF project. The system has 7 WCF services, will grow to 9, each self-hosted in a seperate console app/windows service. All of them are single instance

Architect desperately wants to use SOAP over JMS

喜你入骨 提交于 2019-12-09 11:00:23
问题 I have used JMS in the past to build application and it works great. Now I work with Architects that would love to use the Spec : SOAP over Java Message Service 1.0. This spec seams overly complicated. I do not see many implementation (Beside the vendors pushing for the spec). Does anyone here is using this specification in a production environment? What is your main benefit of using this spec? Link: http://www.w3.org/TR/2009/CR-soapjms-20090604/ 回答1: I had the bad luck using SOAP over JMS.