Skip to main content

Oracle develop roadshow in Moscow, 4-5 th february

Last week Oracle corporation demonstrated their roadshow in Moscow. The roadshow started with the sparkling presentation of Larry Cable. Within an hour he could manage to demonstrate the Oracle Big Fussion middleware, focused on Oracle WebLogic Server and related (Java based) standards technologies. It was very interesting to listen JAVA/RICH ENTERPRISE APPLICATIONS TRACK and enjoy the ability of Oracle JDeveloper. I always against Oracle strategy to make JDeveloper as a main IDE to develop all the java related technology on Oracle platform, because it's seems all the eggs in one basket. But while Larry go through all the the ADF rich client with some mouse click, i started believe that may be JDeveloper already got maturity to use seriously.
There were three main Track:
DataBase Track and hands on lab;
Java/Rich enterprise Application track and hands on lab;
Service oriented architecture track and hands on lab.

I was very interested on SOA track, specially on BEA products. This track covers all things service-oriented architecture (SOA), from basics to best practices. Also covers architecture role on small and large enterprise application. This track also focused on emerging trends such as business process management (BPM) and event-driven architecture. I love the technical deep drive on BPM suite and BPA suite and the Oracle Business Rules engine. The overview of SCA was very interesting, now Oracle has their own implementation of SCA on their basket.
One of my friend convince me to attend on Database track named "Doing SQL from PL/SQL: Best and Worse Practices", it was wonder full to learn about the new features of PL/SQL and the worst practices.
In the conclusion i can only say that, i was satisfied and be sorry for those who missed the roadshow.

Comments

Post a Comment

Popular posts from this blog

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Analyse with ANT - a sonar way

After the Javaone conference in Moscow, i have found some free hours to play with Sonar . Here is a quick steps to start analyzing with ANT projects. Sonar provides Analyze with ANT document to play around with ANT, i have just modify some parts. Here is it. 1) Download the Sonar Ant Task and put it in your ${ANT_HOME}/lib directory 2) Modify your ANT build.xml as follows: <?xml version = '1.0' encoding = 'windows-1251'?> <project name="abc" default="build" basedir="."> <!-- Define the Sonar task if this hasn't been done in a common script --> <taskdef uri="antlib:org.sonar.ant" resource="org/sonar/ant/antlib.xml"> <classpath path="E:\java\ant\1.8\apache-ant-1.8.0\lib" /> </taskdef> <!-- Out-of-the-box those parameters are optional --> <property name="sonar.jdbc.url" value="jdbc:oracle:thin:@xyz/sirius.xyz" /> <property na...
Post a Comment
Read more

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...
Post a Comment
Read more