Masterclass for Java Developers – Make that Database Work for You! 17th December 2010

Lucas Jellema 3
0 0
Read Time:2 Minute, 5 Second

Really getting the most out of your database. That would be nice, given wat databases can do (and what you may have paid for them).

Few serious Java Applications are completely devoid of interaction of some kind with a database.

However, most ORM and  Java Persistency frameworks do their utmost to hide the database and all it can do from the Java application and very few Java developers can truly leverage the full capabilities of the database their application works with. For all intents and purposes, the database in many cases is still nothing more than a flat storage cabinet.

On 17th December I will present a Masterclass that demonstrates how Java applications can benefit from the functionality on offer from underlying databases in a way that does not impact the application architecture, introduces breaches of open standards or creates undesirable coupling. Using plain JDBC, JPA frameworks and alternative interaction channels – for example http-based RESTful interaction – this seminar demonstrates through many examples how [Java] applications can become better performing, more elegantly designed and more productively developed as well as more scalable and robust.

The outline of the day is as follows:

  • Power of SQL
  • Introducing Stored Procedures & Triggers
  • Encapsulation of the Data Model
  • Caching & Refreshing
  • Business Logic & Data Constraints
  • Fine Grained Security
  • Multi-Tier architecture with Java and RDBMS

The masterclass is targeted at experienced Java developers with at some exposure to JDBC and ORM frameworks (ideally JPA as well). Some knowledge of SQL is strongly desirable.

The seminar will  provide attendees with a good understanding of what a database can contribute to Java applications – where its strong suits are, what its role should be in the architecture. They will also learn how the special characteristics of an RDBMS can be leveraged by the Java application – without sacrificing the multi-tier architecture, principles of encapsulatation  and decoupling. We will discuss how we can maintain database independence while also engaging each RDBMS product’s specific characteristics.

The database used in the demonstrations and code samples will be Oracle RDBMS. Most of the principles and features apply to other databases too. However, some special Oracle features – such as Flashback Query and Total Recall, Database Query ResultSet Change Notification, Analytical Functions, Application Context, Virtual Private Database, Materialized Views, HTTP interaction are discussed and demonstrated in addition to more generic Java-RDBMS interactions.

More information about this masterclass and for registration, please see http://www.amis.nl/amis-masterclasses/oracle-database-in-java-applications.

About Post Author

Lucas Jellema

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

3 thoughts on “Masterclass for Java Developers – Make that Database Work for You! 17th December 2010

  1. Hi Lucas,
    I am interested in the master class. can you please share the presentation (PPT) or the complete Agenda of the class.
     
    Thanks
    Tousif

Comments are closed.

Next Post

Pipelined Table Functions

I have had trouble with a certain view I have to create at the customer site I am currently working at. The view involves 3 SQL queries combined by using a UNION ALL, since the separate queries are mutually exclusive. Using the UNION ALL makes it a bit faster since […]
%d bloggers like this: