September 2005

Monthly Archives

CodeFutures Announces Technology Partnership with seeMore Technologies

PRESS RELEASE

CodeFutures Announces Technology Partnership with seeMore Technologies

[ Denver, CO , September 30, 2005] CodeFutures has integrated its FireStorm/DAO data persistence tool with the seeMore virtual database platform. The result is that enterpises can very quickly develop applications that require data from multiple data sources.

“The seeMore virtual database approach allows the real data to stay in situ and be accessed in real-time. There is no data warehouse with data replication problems. For Java developers using FireStorm/DAO, a vitual database looks and feels like a normal database.” says PJ Murray, CEO, CodeFutures Software

“FireStorm/DAO really impressed me in the way it removed the complexity of working with Java Data Access Objects and provided an immediate ROI. It’s a Java developer’s dream tool.” explains Phillip Carruthers, CEO, seeMore Technologies.

“The seeMore virtual database technology is remarkable in the way that it really looks and feels like a real database, despite the fact that the data can be spread out throughout an enterprise. The product is so well designed that it was very easy to integrate FireStorm/DAO with it.” explains Andy Grove, CTO, CodeFutures Software

FireStorm/DAO is available in Enterprise , Architect, and OEM editions. FireStorm/DAO Architect Edition allows new custom code generation templates to be developed and integrated with the FireStorm/DAO Studio environment. FireStorm/DAO Architect Edition includes the source code for the Java code generation templates.

Additional information on FireStorm/DAO is available here:

/products/firestorm/

A video demonstration is available here:

/library/FireStormProductDemo.wmv

Additional information on Data Access Objects is available here:

/data-access-object

FireStorm/DAO is available for free evaluation from:

/products/firestorm/download/

The FireStorm/DAO Enterprise Edition is priced at $595 per developer. FireStorm/DAO Architect Edition is priced at $3,495 per developer. There are no runtime deployment licensing fees.

About seeMore Technologies

seeMore Technologies is a provider of Corporate Data Operating System(tm) technologies through its Virtual Database Server technology for Enterprise Information Integration. seeMore’s mission is to address a growing phenomenon within today’s business infrastructures – the proliferation of multiple data sources across single organizations, multiple locations, across the supply chain and on the Web, and the increased need to utilize this information as if it were a single data source. www.seemoretechologies.com

About CodeFutures Software

CodeFutures is the leading supplier of Java software development products for advanced data persistence. The benefits provided by CodeFutures’ approach are higher developer productivity, better software quality, and lower maintenance costs. CodeFutures’ first product, the award-winning FireStorm/DAO, makes software developers more productive by generating the Java code for accessing relational databases.

CodeFutures’ code generation approach provides faster and cheaper application development, higher quality applications, more predictable and consistent results, faster software product development cycle times, faster time to market for commercial application development, reduced project costs, and reduced project risks. CodeFutures approach ensures that the focus of software developers is solving business problems.

CodeFutures’ products are used by corporate Java software programmers in sectors such as television (BBC Technology, Turner Broadcasting), finance (Lehman Brothers, JP Morgan), military systems (BAE, Lockheed Martin), government (Missouri Lottery, Port of Barcelona), IT consulting (Siemens Business Systems, LogicaCMG, BearingPoint, SDS, IBM), retail (MetCash, Ahold USA), high technology (EMC, Macromedia), and industry (Suzuki, AREVA).


CodeFutures Announces Technology Partnership with seeMore Technologies

CodeFutures Announces Technology Partnership with seeMore Technologies

CodeFutures has integrated its FireStorm/DAO data persistence tool with the seeMore virtual database platform. The result is that enterpises can very quickly develop applications that require data from multiple data sources.”The seeMore virtual database approach allows the real data to stay in situ and be accessed in real-time. There is no data warehouse with data replication problems. For Java developers using FireStorm/DAO, a vitual database looks and feels like a normal database.” says PJ Murray, CMO, CodeFutures Software

“FireStorm/DAO really impressed me in the way it removed the complexity of working with Java Data Access Objects and provided an immediate ROI. It’s a Java developer’s dream tool.” explains Phillip Carruthers, CEO, seeMore Technologies.

“The seeMore virtual database technology is remarkable in the way that it really looks and feels like a real database, despite the fact that the data can be spread out throughout an enterprise. The product is so well designed that it was very easy to integrate FireStorm/DAO with it.” explains Andy Grove, Chief Architect, CodeFutures Software

FireStorm/DAO is available in Enterprise , Architect, and OEM editions. FireStorm/DAO Architect Edition allows new custom code generation templates to be developed and integrated with the FireStorm/DAO Studio environment. FireStorm/DAO Architect Edition includes the source code for the Java code generation templates.

About FireStorm/DAO

FireStorm/DAO is a database access tool that adopts a pragmatic approach of generating Java source code for data persistence that is a direct mapping of a particular relational database schema. It is also possible to define complex multi-table queries and to leverage existing database logic contained within stored procedures.

FireStorm/DAO is based on the Data Access Object design pattern and is available in Enterprise, Architect, and OEM editions. FireStorm/DAO Architect Edition allows new custom code generation templates to be developed and integrated with the FireStorm/DAO Studio environment. FireStorm/DAO Architect Edition includes the source code for the Java code generation templates. The code generation templates are written in Java, which means that Java developers have a very short learning curve before they can start customizing the code generation.

Additional information on FireStorm/DAO is available here:
/firestorm/

FireStorm/DAO is available for download here:
/products/firestorm/download/

About CodeFutures

CodeFutures is the leading supplier of database performance tools. The benefits provided by CodeFutures’ database access tools are higher developer productivity, better software quality, and lower maintenance costs. CodeFutures’ first product, the award-winning FireStorm/DAO, makes Java software developers more productive by generating Java DAO ( Data Access Object) code for accessing relational databases.

CodeFutures’ products are used by corporate Java software programmers for Java persistence in sectors such as television (BBC Technology, Turner Broadcasting), finance (Lehman Brothers, BACS), military systems (BAE, Lockheed Martin), government (Missouri Lottery, Port of Barcelona), IT consulting (Siemens Business Systems, LogicaCMG, BearingPoint), retail (MetCash, Ahold USA), high technology (EMC, Macromedia), and industry (Suzuki, AREVA).


Enterprise Software Product Pricing

Enterprise Software Product Pricing

We’ve worked very hard at CodeFutures to make our product pricing transparent, open and fair, predictable and stable, justifiable, technically workable, and of course, economic.I wonder how many vendors can claim that?

For example, you can immediately exclude any vendor that does not publish its product pricing. Not publishing product pricing immediately raises many doubts about whatever price is quoted by a software vendor.

Transparent Pricing

Software product pricing must be meaningful and understandable by customers. The pricing mechanism must be related in some way to the software is used. That’s one of the reasons that, for example, an annual subscription per user works really well. You can simply determine if it is really worth that much per year for each user. CodeFutures’ Premium Support, which includes all product upgrades, is essentially an annual subscription.

It may seem obvious that pricing should be readily understandable for customers. In fact, it should be so simple that customers understand your pricing in a few seconds.

For a developer tool, transparent pricing almost certainly means pricing per developer, rather than per installation. That’s fairer because developers often have multiple development machines. But it’s also transparent because it’s clear to the end user what the license fees are – no hidden costs.

Open and Fair Pricing:

Product pricing should be published and clear. Why do software vendors hide their product prices? Do you charge widely different prices to different customer based on their ability to pay?

Fair pricing means avoiding unfair discrimination between different classes of customer and usage. For example, a lot of US software vendors charge higher prices in Europe for no particular reason other than they feel they can get away with it. Also, there’s many examples of different prices for different categories of customer – with higher prices for industries such as banking.

Predictable and Stable Pricing

Customers can predict how much the FireStorm/DAO and Premium Support is going to cost – there are no hidden charges. One of the worst practices in the software industry is to offer very low entry fees but then charge increasing support fees in later years once the software is installed. There’s a few software vendors in that seem to have an acquisition policy based on buying other software vendors with a large installed based of software that’s difficult or inconvenient to remove, and then start to squeeze the customers by increasing the price of ongoing support. New product releases and the innovation that won the customer base in the first place is long forgotten.

Another unfair practice is to change pricing models for existing customers. The introduction of dual core processors, for example, is prompting some software vendors to suggest that they should charge more (or even twice as much) per CPU because the CPU is better architected (really! this is despite the fact that CPUs doubled in power every 18 months for the past 20 or so years). That would mean that an existing customer that migrated to a new hardware platform might be punished with higher support fees.

Justifiable Pricing

It’s often difficult to see why two similar software products have vastly different prices. But it happens all the time with software: OpenOffice versus Microsoft Office, JBoss versus WebLogic, MySQL versus Oracle.

When it comes to enterprises using software, price is only one of many factors. That’s why commercial products can exist beside very similar free alternatives. For an enterprise looking at an open source product ‘vendor’, it’s necessary to understand and have faith in the business model that involves giving away the primary asset.

So how does CodeFutures justify the price of its DAO generator? We’ve provided a DAO benefits Web page that anyone can access that explains how the product cuts development costs.

Technically Workable Pricing

From the software vendor’s point of view, the product pricing mechanism must be technically feasible and efficient to administer. This partly relates back to the requirement to make the product pricing as simple as possible.

Economic Pricing

There are several business models for selling software. The traditional model is up front license fees, with ongoing support if it’s a product used in enterprises. The product price must be able to support a reasonable return for the software vendor. If market forces, such as open source competitors, force the prices down, it might no longer be economic to sell the software. One of the best examples, perhaps, in the Java space, is what Eclipse has done the Java IDE market. You can imagine the pain felt by Borland, etc.

The IBM business and pricing model is gaining traction with independent software vendors – sell a solution – solve the customer problem – using a combination of packaged software and professional services. What is nice about this pricing model is that it does deliver results for the customer.

Subscription Pricing

The future of the software industry seems to be in subscription pricing. It should eliminate a lot of the worst sales practices in the industry that develop due to the sales incentives around large up front payments – customer pay for what they use, vendors need to keep their customers happy to keep the subscription revenue flowing. It means that the sales team is focussed on long term customer satisfaction and it means that software vendors have a steady revenue stream. Customers benefit because the focus is keeping the customer base happy rather than chasing new revenue.

PJ Murray
CodeFutures Software


Java Boutique: FireStorm/DAO Product Review

Java Boutique: FireStorm/DAO Product Review

Java Boutique has published a FireStorm/DAO product review:http://javaboutique.internet.com/tutorials/codefutures/

Java Boutique is a great resource for good quality articles on Java topics, so we’re very happy a product review has been published.

PJ Murray
CodeFutures Software


EJB 3.0 Persistence: A question of when rather than if

EJB 3.0 Persistence: A question of when rather than if

We’re starting to get some questions about adding support for new EJB 3.0 Persistence specification. The response is yes, of course we’re going to support the new specification. Without doubt, when the specification is approved, it will be a very big event in the Java community. The specification is expected to be finalized in the first quarter of 2006.So the next next question is: when should the EJB 3.0 Persistence feature be added to FireStorm/DAO?

For CodeFutures, its a question of appropriate timing. Do we go ahead with implementing the current draft of the specification when it will probably change (and improve) over the next few months?

What added benefit is there in providing an early implementation of the specification?

There’s already other Java product vendors building technology previews. Oracle, for example, is doing excellent work (but seems to be suggesting that developers use the technology previews of an incomplete specification in real projects?).

So the CodeFutures plan is to start implementing the specification once it is solidified. Then release a GA product based on the specification after it is approved by the JCP.

Will CodeFutures be recommending using EJB 3.0 Persistence in real projects? That remains to be determined.

The issue is that it’s a new specification based on input from multiple, divergent sources where compromises must be made. It’s very rare to get all the details right in the first version of a specification. In fact, it would possibly be a unique achievement.

So CodeFutures may end up recommending that customers developing important enterprise applications should wait for EJB 3.1 Persistence.

Iif you’ve got spare time, certainly experiment with the EJB 3.0 previews.

CodeFutures would appreciate any comments, good, bad, and ugly, you have on EJB 3.0 Persistence.

In the meantime, we’re looking at Service Data Objects as the next generation for Java persistence.

PJ Murray
CodeFutures Software