Vladimir Shcherbina

Greenhorn
+ Follow
since Nov 15, 2005
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Vladimir Shcherbina

Hello,

Did your book address address such issues as inference analitics of dependencies between events?
Best,
Vladimir
1 month ago
Hi Deepak,
Can Dockers applications use GPU concurrently?
Best Regards,
 Vladimir  
Hi Deepak,

 We are developing with RTP H.264 and transport streams (audio, video and data) applications, that should coexist on the same machine and therefore, should be isolated. Currently, these are based on MS DirectShow, but we are in the process of transitioning to gstreamer/Linux. Is Dockers right approach for their deployment?
Many thanks in advance for your answe4r,
Best Regards,
Vladimir
Could it be recommended as a crush course for Google questions on theme?
2 years ago
Hi,

I am new in AWS so the question is: there any trial/test option for deployment of educational toy project, which is not expensive or even free?
3 years ago
Hi,

Is AWS good for interactive video applications across the Internet?
Suppose, I want to provide to customers in other country ability to manage a camera of drone in real time for marketing purposes. All software currently in Windows C++ C#.
Many thanks for your answer.
3 years ago
Hello,

Why SCA is better than other services composite applications? We can connect components in BPEL execution environment or just using some tooling that enable an easy connection of various components to some ESB?
Vladimir

Simon Laws wrote:Hi

Good questions.

1. Is SCA the same as SOA? If not, what exactly the differentiating factors?

For me they are not one and the same. SOA describes architectural patterns for building distributed systems from services. SCA describes and XML based programming model for describing components, the services they provide and how can be connected to other components. It does this independently of technology by allowing you to build components using your favourite language and connected them using your favourite binding technology. It just so happens that using SCA you can build systems that exploit the same architectural patterns that SOA recommends.

2. What is the core concept behind SCA?

The core concept is the SCA assembly model. An XML model that describes components and the way that they are connected. A quick example of this XML is probably the easiest way to describe it. Take the Payment composite from the book example;

<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
targetNamespace="http://tuscanyscatours.com/"
name="payment">

<component name="Payment">
<implementation.java class="com.tuscanyscatours.payment.impl.PaymentImpl" />
<service name="Payment">
<binding.ws uri="http://localhost:8081/Payment" />
<binding.sca />
</service>
<reference name="customerRegistry" target="CustomerRegistry" />
<reference name="creditCardPayment">
<binding.ws uri="http://localhost:8082/CreditCardPayment" />
</reference>
<reference name="emailGateway" target="EmailGateway" />
<property name="transactionFee">0.02</property>
</component>

<component name="CustomerRegistry">
<implementation.java class="com.tuscanyscatours.customer.impl.CustomerRegistryImpl" />
</component>

<component name="EmailGateway">
<implementation.java class="com.tuscanyscatours.emailgateway.impl.EmailGatewayImpl" />
</component>

</composite>

We've defined three components "Payment", "CustomerRegistry", "EmailGateway". Note that the components are implemented with Java classes using implementation.java in this case. This can be replaced with other implementation types, for example,

<component name="Payment">
<implementation.spring location="Payment-context.xml"/>

or

<component name="Payment">
<t:implementation.script script="payment/PaymentImpl.py"/>

or

<component name="Payment">
<implementation.bpel process="pp:Payment"/>

etc.

Note that the Payment component described service and references. Services are what other components connect to. References are how you connect to other components.

We use binding.ws in the service and in the "creditCardPayment" reference. This is saying that you want web services for the service and for that reference. If you want to use other protocols instead you just change these binding elements.

The property element is a way for configuring the component.

Regardless of which implementation type you use this approach to defining services and references and properties remains constant and hence we've disconnected the way that you build the business logic of a component from the way that components are joined together.

So you take this XML and fire it into Tuscany, along with the required resources such as the Java classes being used to implement the components, and Tuscany creates the components and makes the services available for you without you having to code web services apis (in this case).

3. Looks like the definition/introduction on SCA in the manning website (on your book) is resembling Cloud Computing. Is there any relationship between these two?

We've certainly started to look at making that the case. Imagine you want to build a cloud application. E.g. multiple components that are going to interact out there on some virtual infrastructure. Wouldn't it be good if there was some abstract description of the application that you could provide to the cloud infrastructure that tells is what to run. Sounds a bit like the assembly model. We've had a go at running Tuscany apps on various cloud infrastructures. I can point you at more info it you want to look in more detail.

4. Is there any speciality or meaning in the name being chosen as Tuscany?

It was chose before my time but I'm guessing that someone liked Italy so they found a place name with "sca" in the middle of it.

Simon



Yes, such information can be very interesting
Hello,

In IBM, I used to work in Java world, and now I am working on .NET platform. Your book is dedicated to SCA Tuscany Java implementation. Is the SCA mature enough (in my time in IBM it was not ), so one can implement it in the .NET platform with C#? Is there any documentation that can be helpful in this regard.
Many thanks in advance for your help.
Best Regards,
Vladimir Shcherbina
Hi,

How Hadoop related to distributed transactional cache implementations (like IBM ObjectGrid, etc.)?
Also, is Java the only language of choice or something like Erlang can be more suitable for this purpose?
8 years ago

Opher Etzion wrote:Hello Vladimir. The direction we are using in the book is exactly model-driven approach, by which the "event processing network" that contains the flow of events into the different agents that ,for example, detect patterns, is defined in the model level, and this model should be directly compilable into execution. What you mention - static analysis to detect possible deadlocks may be a specific application; there are, of course, a lot more application types that can use such an approach.

cheers,

Opher



I understand I need to see the whole book, not just samples . Is your EPN in the phase of conception or real tool?
9 years ago
Hi,

Is there any MDL that allows event oriented approach to the system modeling? In such way that you can start from well known system events and infer system entities and their relations, or you can build artificial high-level events based on real low-level ones and from this point reveal (or establish) interesting design conclusions of your system?

In my time in CEP, it was a problem of who can catch existing complex events relations in the real system and who can express them in some event-oriented language and how these two will understand each other? I am trying to think in opposite way: one should establish desired complex events dependencies and from that infer some design decisions or make a fruitful analysis of existing system. IMHO, such approach will be useful for static analysis of multi-threading applications i.e. one can express deadlocks as a combination of program events in temporal context and point out to problematic event patterns that need to replaced.
Best Regards,
Vladimir
9 years ago
Hi,

I have a question about iPad, what is a difference between this and MacBook in terms of programming ? (OS, Java, Objective C, iPhone SDK, iPhone simulator, etc.)
9 years ago
iOS
Hello,
My question is about topics that you are covering in your book. Are they strictly binded to Sun Java Architect syllabus or you also trying to accommodate a broader architectural aspects like interoperability with legacy systems, etc.?
Best Regards,
Vladimir
Hello Dhanji,

Are you aware of any integration of Test Driven Development and DI? Are you referring to this subject in your book?
Best Regards,
Vladimir