I’ve been learning a little bit about SOA and Oracle SOA Suite 12c, I barely understand that I can use BPEL Process in a SOA Project and that I cannot use it with Service Bus Project and that SOA Composites are deployed into the Oracle Enterprise Manager, while Service Bus Projects are deployed directly to the Oracle Service Bus.
My question is, does anyone know what are the differences between use SOA Projects and Service Bus Project even if I can consume services or use DBAdapter from any?
Is there any good reason to consume my soap, rest, dBadapters, etc in a BPEL Process in the SOA Project instead of doing it directly in my Service Bus Project?
Thanks in advance for you help,
:)
OSB is generally used whenever your flow is simple and light weight like- just DB call, web service call, message routing with few mappings. It can used as a proxy service (to hide the actual implementation) to the external system who is calling this proxy as a web service.
Whereas, SOA is preferred where the flow is complex with bulk transformation or heavy orchestration involving multiple intermediate calls to third party systems, etc.
You can go through the below link to get more information,
https://community.oracle.com/thread/1077167?start=0&tstart=0
Related
Can I use SOA and three-tier in one application? Using SOAP to connect for external services, using MQ and Spring MVC. I have an application server and server for the database.
Yes, it seems that they are very different things.
There is a vast array of different SOA implementation styles, you can do it in so many ways. One is to have services talking to APIs over http where the APIs in question are written in a 3 tier style.
You can also have an event driven architecture where messages are passed on a message bus or a queue or some sort, the services reading and writing to those queues can be written in a three-tier style.
To sum up yes you can have SOA and three-tier in the same architectural solution, one does not exclude the other.
Does this help your decision on how to structure your service design and how to structure the wider solution architecture?
Background-
I am extremely new to CORDA and Blockchain Platform. In the past few months i have had my share of experience working on a small project on Ethereum as platform. Ethereum blockchain was leveraged as ledger to mark Transaction as a proof of existence. It means for some action (success/failure) we have marked respective transaction on Blockchain. We may consider it as a proof of concept to show knowledge of interaction with nodes running on Ethereum Blockchain.
Infrastructure - Node.js web services, two ethereum (PoA) nodes
Question-
I would now like to port this running example on to CORDA blockchain. How would i achieve this with bare minimum changes. That means if i have a Corda network with two nodes running on my system and i want my web services to connect to one or both of the nodes and save the transaction (in its state). I understand that this certainly is not what CORDA might be meant for. Consider this question as my first step to interact with CORDA from Node.js web services.
Any inputs highly appreciated.
I recommend you go through the documentation first. your Tx will be a state. you need to build contracts and flows for a Tx to happen. Tx will happen using flows which will be initiated using Crash Shell or RPC Client. AFAIK, this client is in Kotlin or Java. so you'll have to create a JAVA or Kotlin application to instantiate this client. now in the Java application, you'll have to expose rest endpoints to communicate with the client which will initiate your flows. you can call these rest endpoints from your node application. All this has to be created in CodaApp. This is the bare minimum.
I just found there is a library.
look at this: https://gitlab.com/bluebank/braid
This can help you.
Is it advicible to build the MSA based services on Oracle SOA or any other ESB suite for that matter? Is there any advantage or disadvantage?
If I am using Java, Spring and JPA over a message queue - say - RabbitMQ, I can achieve it in a more controlled environment with less recurring expenses. Of course will end up mixing tools like Drools or JBPM or similar to achieve things that may be OOTB (Out of the box) in the SOA Or ESB Suite. But scaling a specific service without paying licence fee for an additional environment should certainly be a good catch right?
Microservices architecture pattern applies to development of backend systems/services, whereas ESB (e.g. Oracle SOA Suite) is intended as an intermediary layer between consumers and backend services. Backend services contain rich application logic, whereas ESB services provide only intermediary functions like routing, transformation, orchestration etc.
ESB is not intended for rich application logic, though it's possible to do that.
Using ESB (e.g. Oracle SOA Suite) to host microservices is achievable, but you will get a big overhead comparing to limited functions and scalability. If you are looking for centralized API management (tracing, security etc.), you can put an API gateway into your architecture instead of full scale ESB.
I study SOA and webservices for a science paper. My state of knowledge is, that every SOA architcture needs a service broker.
Webservices are concrete implementations of a SOA, so do they have a service broker after? For example I create a webservice in asp.net which returns "hallo world" By Creating it, do I create a service broker too?
Don't let fool you by answers which are copy paste from Wikipedia :-)
Webservices are concrete implementations of a SOA
This assumption/statement is wrong. At least there is no direct relationship between SOA and webservices. SOA is an architectural paradigm where a webservice is a concrete technology (stack) based on WSDL and its result, the SOAP-protocol. Nothing more. Webservices may help to establish loosely coupled service landscape, which the SOA paradigm expects. But you could also build up a SOA landscape with other technology stacks (self-written hacks, RMI, even based on REST for instance).
Repository
The thing is: When you start building up your SOA-landscape, you (or others) will code services (i.e. webservices) where your service will have a technical contract (WSDL, WADL, ..) as a base for the implementation. Your clients will ask for it and you want it to store somewhere. This somewhere is usually a service repository. You could develop your own one, use the UDDI-standard or just buy one of products by the big vendors (IBM, TIBCO, Oracle etc).
Broker
A message broker within the SOA context is some piece of software, which supports the decoupling of the connected partner systems. Commonly it's called ESB (enterprise service bus). Also one of the goals of the SOA paradigm is, that the services can be used by anyone (reusability). Therefore you don't want to connect your services by P2P-connections (aka spaghetti architecture) - just imagine that one of the service participants changes it's hardware/IP: this would be a nightmare for all the connected partner systems. That's why the ESB was invented which acts between the service consumer and the service provider.
Typically, these ESB-products support a lot of technologies or -stacks/APIs like HTTP, JMS, REST etc.
Source: I work with a self-claimed SOA landscape and thousands of different (web-)services for a big company for a long time now.
A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.
Web services are self-contained, self-describing modular applications that can be published, located, and invoked across the Web.
A network component in a Web Services architecture can play one or
more fundamental roles: service provider, service broker, and service
client.
Service brokers register and categorize published services and provide search services. For example, UDDI acts as a service broker for WSDL-described Web services.
I am building a new Java EE application (thin client), and here is the application layers:
The application presentation will be with JSF2 / Spring webflow and RichFaces 4
The businees layer will be with EJB 3
The Persistance layer will be with JPA2 - Hibernate implementation
The application will run on Websphere Appliccation server.
The company owns Websephre Message Broker as an ESB.
I have got two choices, and i am trying to find out the best depending on the scalability, maintenance, performance, Best practices and entreprise architecture design, for each of them:
Deploy the business EJB3 Services on the ESB and deploy the presentation layer on a dedicated server: The presentation Layer will call the business services through the ESB
Deploy the EJB services on a dedicated WAS and deploy the presentation layer on a dedicated server: The presentation Layer will call directely the EJB services without using the ESB
It depends (as always :) ) If you plan to extend your application in the future and integrate it with other clients apart from the JSF client then ESB would be a viable solution. Else keep the things simple, i.e. everything in an application server. In case you proceed with the ESB I recommend you moving the EJB layer to the application server and exposing your application from the ESB as web services.
Here's my rec.... build your app on WAS using the architectural decisions you've made. For integration of your app to the ESB, I would vote for JMS or WebSphere MQ. You could opt for web services but as your enterprise architecture team would most likely say.... you need to have time independent communications with confirmed delivery.
If you want to also see how this all works, I would look at the IBM SOA Design Patterns or feel free to read my Redbook (IBM SOA Retail Design Patterns) for an idea of how to glue apps to the ESB.