|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
News
News
News
|
Messages: 7
Messages: 7
Messages: 7
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
FastObject.NET - native object database for .NET
Versant Software has released the FastObject.NET class persistence framework capable of storing your objects into a native, object-oriented database. Using metadata tags you can add persistent attributes to make objects persistent capable.
The product includes support for inheritance (you can choose any subset of hierarchy), collection mapping, and private members mapping using properties.
FastObject.NET uses operating system files to store its data the same way desktop databases do, like MS Access and FoxPro. However, usage of the .NET version will be limited until server-side database connectivity is available. Versant currently does have such a product, called t7, but .NET is currently not supported.
Versant's product line seems to be confusing - they offer both O/R and native object persistence for Java (Kodo and FastObjects), a server-side solution for Java and C++ (t7), and a desktop framework for .NET. Comments and thoughts are welcome.
Product tutorial http://www.versant.net/eu_en/solutions/dotNet_en http://community.fastobjects.com/community_fastobjects_net.htm
|
|
Message #119851
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
FastObject.NET - native object database for .NET
I found the read on Versant's page really fascinating. I haven't seen a model quite like this for use in the persistence of objects, but I've seen products that attempt to store objects in the same way.
A number of intriguing questions arise on something like this (obviously, they all can't be answered now, but the proliferation of object mapping technologies are causing these questions to rise in importance):
1) I didn't see a trade off analysis on Versant's site as to when a model such of this should be used instead of a more traditional relational model. I wonder if anyone has done some analysis as to best case scenarios for one over the other?
2) Are there J2EE products that approach the problem the same way and how they perform in the marketplace in comparison to more traditional OR technologies?
One of the things you should consider is contacting Bruce Martin at The Middleware Company. He's been working on a specification that TMC will publish that will enable TMC to perform productivity and performance analysis on object-relational products. He's been talking to various vendors and this looks like a technology that may have a fit in his research. His email is bruce@middleware-company.com.
|
|
Message #119882
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
FastObject.NET - native object database for .NET
I didn't see a trade off analysis on Versant's site as to when a model such of this should be used instead of a more traditional relational model. I wonder if anyone has done some analysis as to best case scenarios for one over the other?
The best analysis on the subject Ive seen, is made by Martin Fowler in his book Patterns of Enterprise Application Architecture (ISBN 0321127420).
To sum up; the more complex your domain and business rules, the more to gain with a domain-driven approach over a relational.
Regards, // Martin Rosén-Lidholm
|
|
Message #120851
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Indeed.
It does ease the burden of implementation. There is a cost however, you lose the ability to interface with the data that is being persisted. This can be a huge problem especially when trying to build systems that can interface with one another.
The other major issue with persistance engines is that there is no standard object query syntax. One can retrofit SQL to do the querying, or use XPath, as in projects like Bamboo. The problem with this is that it's often difficult to debug or test your queries in the development process.
The major barrier to adoption for these types of persistance engines is the lack of an industry agreed upon method for putting data in, and getting it out.
|
|
Message #122085
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
CORRECTIONS
Hi,
sorry for my late reply, but there are a couple of wrong statements contained in the initial posting, here the corrections:
1. FastObjects .NET targets our native OODBMS AS WELL AS relational databases, currently IBM DB2, MS SQL Server and Oracle are supported.
2. FastObjects .NET does NOT rely on properties at all! FastObjects .NET utilises a very sophisticated code enhancement technique, that makes it possible, to support private and public fields and this approach is much faster then reflection-based approaches.
3. MOST database systems can use/do use operating system files. Take a look into your Oracle installation, I would call it operating system files, where your data is contained in ;-)
4. Server-side database connectivity has ALWAYS been available! Only our Trial Edition does not contain the server executable nor the RDBMS support. If you want to evaluate the full product just write an email to: info@versant.net
5. Confusion is created by such postings like the initial one ;-) Versant offers: -Versant VDS with interfaces for C++ and a JDO interface (the JDO interfaces is the Kodo Versant Edition) -FastObjects with interfaces for C++, JDO and .NET, supporting the native FastObjects backend, Oracle, IBM DB2, SQL Server -Kodo with JDO interfaces, supporting a lot of relational databases
This means we offer the right data persistence solution for every platform (Windows, Linux, Unixes, ...), every programming language/framework (C++, Java, .NET) and every backend (OO as well as relational).
Best regards,
Christian Romberg FastObjects Team
|
|
Message #122347
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Indeed.
I agree. One little detail; there is no standard object query syntax. Yes, there is - the OCL of UML. The only product Ive used that uses OCL for this (and other purposes) is Borlands ECO.
Too bad all other ORM/MDA tool vendors seem to choose to make there own object query language. So, unfortunately the major barrier to adoption for these types of persistance engines is the lack of an industry agreed upon method for putting data in, and getting it out. is true after all...
|
|
Message #122372
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Indeed.
FastObjects .NET offers OQL as its query language.
OQL (Object Query Language) is a standardized object oriented query language created by the ODMG, and is syntactically close to SQL.
Best regards,
Christian Romberg FastObjects Team
|
|
 |
| |
|
New content on TheServerSide.NETNew content on TheServerSide.NETNew content on TheServerSide.NET |
 |
 |
Language "mashups" will become more prominent, and developers will become polyglots, one programmer suggests.
SearchWinDevelopment.com offers an introduction to the language, performance, testing and data management improvements in VS 2008.
VBCode.com code snippets cover all aspects of application development, from data binding to security to the user interface.
Get up to date on XAML best practices with a variety of articles, tutorials and webcasts. [SearchWinDevelopment.com]
One team's experience with the VSTS DB edition suggests that it can improve workflow for dev teams. It also enhanced Agile efforts.
(June 24, Article)
Microsoft has begun to include DSL tools in the VSTS kit. A new book by Steve Cook and other VSTS team members helps set the stage.
(June 24, Article)
Cartoon: Be it ever so humble there is no place like your home after you get a Microsoft Home Server .
(June 18, Cartoon)
Microsoft's Thom Robbins says new technology to highlight in NET 3.5 includes AJAX, LINQ for both C# and VB, as well as tooling enhancements intended to ease the task of building WPF, WF and WCF apps.
(June 29, Podcast)
Venkat Subramaniam discusses AJAX bottlenecks, the tenets of Agile development and more. He spoke at the Ajax Experience.
(June 25, Tech Talk)
In the second of a two-part series, Michele Leroux Bustamente discusses design decisions related to the claims-based security model. Read the story and walk through the process for creating a set of claims-based utilities to encapsulate claims authorization at the service tier.
(May 24, Article)
Understanding why the Entity Framework exists and learning where it can fit into your projects can get you prepared for the eventual release early next year.
(May 10, Article)
Resource: This learning guide gives you quick access to useful links on Windows Communication Foundation security information.
(April 24, Article)
TSS.NET's Jack Vaughan spoke recently spoke with Microsoft's Brad Abrams to find out what he is seeing in the field and what the chefs in Redmond are cooking. Along the way he discusses patterns of AJAX frameworks.
(April 11, Article)
In a two-part series, Michele Leroux Bustamente explains how claims-based security is supported by WCF, and how you can implement a claims-based security model for your services.
(March 29, Article)
Windows Workflow Foundation is a new technology that many developers will need to get their heads around. In a brief excerpt adapted from Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C#, K.Scott Allen considers aspects of workflow definition.
(March 22, Chapter Excerpt)
|
|