Using Derby as a Network Database Server Engine
- Sep 21, 2007
- Nonlinear Code Management in EJB3
- Database Access via C# ADO.NET
- C# Reflection
- Object Relational Mapping and Java Persistence: Data Modeling and Legacy Schemas
- C# GUI Programming
- C# Assembly Programming
- Using the C# system.io Namespace
- Using C# Generics
- An Introduction to Concurrent Java Programming
- Using C# Interfaces
- Getting Your Software onto Linux
- What’s Wrong with Modern Software Development?
- Building a Solid Foundation for JPA and Hibernate
- Java Patterns for MPLS Network Management, Part 2
- Java Patterns for MPLS Network Management, Part 1
- Getting Started with Spring Web Flow
- Application Contexts for Spring Web Services
- Spring Web Services with SOAPUI
- Hit the Ground Running with the Spring Framework
- Building Multithreaded C# Applications
- Hosting an LDAP Server in VMWare
- Integrating Linux Into Your Windows Environment
- Understanding C# Object Serialization and Object Graphs
- Further Subversion Steps: Get Motoring with TortoiseSVN
- Further Steps with the Java Sound API
- 5 Easy Steps to Using Virtualization Technology
- Five Steps to Getting Started Server-Side with PHP
- Targeted Client Upgrades: Creating a Flexible, Low-cost Application Upgrade Mechanism
- Java DMK and Legacy IT Management
- Aspect-Oriented Programming: A Tool for Internationalization
- Achieving Separation of Concerns Using BPEL
- Mobile Java with J2ME
- Graph Algorithms in Java
- Design Patterns in Java: The Observer
- Five Steps to Managing Unstructured Data with Derby
- Using the Java Sound API
- Moving C++ and Java Programmers Up the Value Chain
- Java Nuts and Bolts: Copy Constructors, Cloning, and Linked Structures
- Further Steps with Derby: Derby Embedded in a Browser
- Further Steps with Derby: Defining and Accessing Your Data
- IT Management Using C# with WMI
- Using Derby as a Network Database Server Engine
- Five Steps to Further Success with Subversion
- Improve Software Installation with AntInstaller
- Multithreaded Java GUI Programming
- The C++ Strategy Pattern for Multiple Network Events
- Java Collections and Iterators
- The C++ State Pattern for Network Operations
- C++ Nuts and Bolts: Casts, Call-by-Reference, and Inheritance
- Getting Started with Subversion on Windows
- Getting Started with Derby
- C# Callback and Event Mechanisms
- Some Rules for Safer Java Programming
- Inheritance and Polymorphism in C++ and C#
- IT Management: Dipping into the Platform with C#
- C# and IT Management Infrastructure
- C++ to C# Migration
- Service Oriented Architecture with Apache Axis
- Speech-Enable Your Java Software
- Generic C++ for Networks
- C++ Inheritance and Polymorphism
- Thinking Recursively with C++
- Aspect-Oriented Programming for Production Code
- C++ Modularity with Namespaces and Exception Handling
- C++ Chain of Responsibility Pattern: Network Events
- The Web Services Distributed Management (WSDM) Standard
- MPLS Network Design Nuts and Bolts
- BPEL: The Next Big Thing in Software?
- On-Demand Computing: A New Paradigm
- Software Plasticity with Aspect-Oriented Programming
- Parser Configuration in JAXP
- Publish and Subscribe Using C++ and the Observer Pattern
- Java Application Servers: Seven Things You Should Know
- Legacy IT Management using C++
- Software Futures: Architecture
- Saving Money with Legacy Data
- Saving Money with Legacy Source Code
- MPLS and Ethernet: Seven Things You Need To Know
- Quality of Service, Part 2 of 2: Managing Enterprise QoS
- Quality of Service, Part 1 of 2: Elements of Enterprise QoS for Voice Over IP
- The Need for Autonomic Computing
- A Blade Server Primer
- Workflow-Based Network Management
- SNMP Versus Command-Line Interface (CLI) for Network Management
- Security and the Management Plane, Part 2
- Security and the Management Plane, Part 1
- Network Management and MPLS
- Managing Large Networks: Problems and Solutions
- Getting off the ground with your first iPhone app
My first iPhone app – “The Day Was…” has now been through two updates. I want to talk a little about how to get started with this interesting technology. As with any software, the first step is having an idea, i.e., one or more requirements.
- On Updating my first iPhone app
I recently applied my first update to my iPhone app – “The Day Was…”. As with many things in the technology world, an update is easier than getting the app into the store – the blank slate problem! Just a little bit of wrestling with the app binary is required and you use the same distribution profile as for the first submission.
- Getting my first iPhone app into the App Store
Having just posted my first iPhone to the App store, I wanted to briefly describe the experience and at the same time to debunk some myths I’ve heard about since I started.
- SOA and IT Strategy
It's a rare organization that has a comprehensive IT strategy. Why does a strategy matter? For one thing, IT is now part of the DNA of all organizations. So, an effective strategy is a key business element.
- IT staff and contractors - why they matter
IT salaries and contract rates in free fall
- A day in the life of a software contractor - Forming good relationships
I wanted to share a few findings with you about my recent forays into the world of software contracting.
- The path to programming excellence ? C++ to Java from C, Pascal and others
I’ve probably used more programming languages down the years than is good for me. And like many other programmers, I mostly use Java nowadays. During my most recent product development, I made a foray back into C in order to do some Ethernet protocol analysis. Some languages are just better than others for such tasks - remember C is a system language so you can use it to dig right into the platform. Java is more constrained because of the JVM boundary. In the end, I integrated the down-to-the-metal C code right back into Java using JNI.
- Moving up the value chain
Following on from my previous posting on decision-making quality, I wanted to talk a little about the related subject of the value chain.
- Decision-making Quality
The need for forward momentum is perhaps one of the negative consequences of the fast pace of modern life. This issue is discussed in ex-world chess champion, Garry Kasparov’s latest book “How life imitates chess”. Kasparov feels that decision-making suffers if insufficient time is taken. He’s not alone. Edward de Bono – the inventor of lateral thinking once said that apart from extreme emergencies there is rarely a need to think quickly. Warren Buffett moved his offices out of
Like this article? We recommend
Apache Derby -- Off to the Races: Includes Details of IBM Cloudscape
The initial promise of Derby has been its applicability to embedded solutions—i.e., situations in which a complete light-footprint database engine is incorporated into a small software component or environment. In this context, Derby really delivers on the promise of component-oriented development because with it you can embed a standalone database into an application based on a browser. This aspect of Derby has received much attention, and you can follow up on this by studying the detailed examples that come with Sun's Derby distribution. However, Derby has another side that hasn't received so much attention: It can function as a network database server engine. This is an interesting development because it might potentially start to compete with the established vendors in this space.
In this article, I want to introduce you to the network server side of Derby. As with my other article on the embedded version of Derby, I'll use some of the example programs that come bundled as part of the Derby distribution. So, if you don't already have one, the first thing to do is get yourself a copy of Derby from the Apache web site. It also 'might not be a bad idea to read my earlier Informit article ("Getting Started with Derby") to get acquainted with the embedded framework and the general Derby philosophy. So, while this article builds on the previous one, it's not mandatory that you read both.
The Network Server Framework
The Derby network server framework, on the other hand, differs from the embedded framework in that the former provides a continuously running server-style Java application that allows multiple, remote JDBC applications to connect to Derby. The major difference between the embedded and network-server frameworks is that the latter allows applications from multiple JVMs to access the same database. This database is the one provided by the network server and the multiple JVMs that access it are the clients. So, the network server framework frees you from the restriction of the embedded framework where all access must be from within the one JVM.
Account Sign In
View your cart