Monday, April 28, 2008
Looking forward to JPA2
A new article by Mike Keith (Oracle / Toplink). He introduces some new cool features of JPA2.
Looking forward to JPA2
A new article by Mike Keith (Oracle / Toplink). He introduces some new cool features of JPA2.
OpenXava
http://java.dzone.com/announcements/openxava-301-jpa-application-e
I like the notion of fully-automated UI tool, not based on source-code generation, like NakedObjects, JMatter, etc.
XIC has its own solution for that, Navilis, which is a component bundled within Xcalia Studio. The main goal is to quickly validate your business model and the corresponding data access layer (mappings, transformations, etc.). It is a little bit like an object inspector (Smalltalk, Groovy) but coupled with some specific tools and widgets for data access (like a query builder, for instance). This kind of component is critical when following the MDA approach.
OpenXava
I like the notion of fully-automated UI tool, not based on source-code generation, like NakedObjects, JMatter, etc.
XIC has its own solution for that, Navilis, which is a component bundled within Xcalia Studio. The main goal is to quickly validate your business model and the corresponding data access layer (mappings, transformations, etc.). It is a little bit like an object inspector (Smalltalk, Groovy) but coupled with some specific tools and widgets for data access (like a query builder, for instance). This kind of component is critical when following the MDA approach.
OpenXava
OpenXava
http://java.dzone.com/announcements/openxava-301-jpa-application-e
I like the notion of fully-automated UI tool, not based on source-code generation, like NakedObjects, JMatter, etc.
XIC has its own solution for that, Navilis, which is a component bundled within Xcalia Studio. The main goal is to quickly validate your business model and the corresponding data access layer (mappings, transformations, etc.). It is a little bit like an object inspector (Smalltalk, Groovy) but coupled with some specific tools and widgets for data access (like a query builder, for instance). This kind of component is critical when following the MDA approach.
OpenXava
I like the notion of fully-automated UI tool, not based on source-code generation, like NakedObjects, JMatter, etc.
XIC has its own solution for that, Navilis, which is a component bundled within Xcalia Studio. The main goal is to quickly validate your business model and the corresponding data access layer (mappings, transformations, etc.). It is a little bit like an object inspector (Smalltalk, Groovy) but coupled with some specific tools and widgets for data access (like a query builder, for instance). This kind of component is critical when following the MDA approach.
OpenXava
Distributed document databases
There is now a kind of global acknowledgement that RDBMS are not well-suited for all new business applications in SOA. I've already mentioned new databases like SimpleDB or Vertica the new project from Michael Stonebraker.
Here is a collection on links about DDD (distributed document databases):
StrokeDB (for Ruby)
http://www.infoq.com/news/2008/04/distributed-db-strokedb
http://strokedb.com/
http://strokedb.com/euruko2008.pdf (nice and innovating kind of presentation)
http://rashkovskii.com/articles/2008/2/14/strokedb-short-intro
CouchDB (written in Erlang)
http://www.infoq.com/news/2007/11/the-rdbms-is-not-enough
http://incubator.apache.org/couchdb/
http://incubator.apache.org/couchdb/docs/intro.html
http://incubator.apache.org/couchdb/docs/overview.html
RDDB (sub-project of CouchDB)
http://rddb.rubyforge.org/
Here is a collection on links about DDD (distributed document databases):
StrokeDB (for Ruby)
http://www.infoq.com/news/2008/04/distributed-db-strokedb
http://strokedb.com/
http://strokedb.com/euruko2008.pdf (nice and innovating kind of presentation)
http://rashkovskii.com/articles/2008/2/14/strokedb-short-intro
CouchDB (written in Erlang)
http://www.infoq.com/news/2007/11/the-rdbms-is-not-enough
http://incubator.apache.org/couchdb/
http://incubator.apache.org/couchdb/docs/intro.html
http://incubator.apache.org/couchdb/docs/overview.html
RDDB (sub-project of CouchDB)
http://rddb.rubyforge.org/
Distributed document databases
There is now a kind of global acknowledgement that RDBMS are not well-suited for all new business applications in SOA. I've already mentioned new databases like SimpleDB or Vertica the new project from Michael Stonebraker.
Here is a collection on links about DDD (distributed document databases):
StrokeDB (for Ruby)
http://www.infoq.com/news/2008/04/distributed-db-strokedb
http://strokedb.com/
http://strokedb.com/euruko2008.pdf (nice and innovating kind of presentation)
http://rashkovskii.com/articles/2008/2/14/strokedb-short-intro
CouchDB (written in Erlang)
http://www.infoq.com/news/2007/11/the-rdbms-is-not-enough
http://incubator.apache.org/couchdb/
http://incubator.apache.org/couchdb/docs/intro.html
http://incubator.apache.org/couchdb/docs/overview.html
RDDB (sub-project of CouchDB)
http://rddb.rubyforge.org/
Here is a collection on links about DDD (distributed document databases):
StrokeDB (for Ruby)
http://www.infoq.com/news/2008/04/distributed-db-strokedb
http://strokedb.com/
http://strokedb.com/euruko2008.pdf (nice and innovating kind of presentation)
http://rashkovskii.com/articles/2008/2/14/strokedb-short-intro
CouchDB (written in Erlang)
http://www.infoq.com/news/2007/11/the-rdbms-is-not-enough
http://incubator.apache.org/couchdb/
http://incubator.apache.org/couchdb/docs/intro.html
http://incubator.apache.org/couchdb/docs/overview.html
RDDB (sub-project of CouchDB)
http://rddb.rubyforge.org/
Amazon adds persistent Storage to EC2
http://www.infoq.com/news/2008/04/amazon-storage
The competition between Amazon, Google and Microsoft around cloud computing is tough.
It is just a raw storage space (e.g. file system) added to EC2, you can use it as you prefer, for instance you can use it to allocate DBMS files. Obviously these storages are persistent, they remain usable after the termination of one EC2 instance.
The link with S3 and SimpleDB is not so clear, but for backup usage.
http://aws.typepad.com/aws/2008/04/block-to-the-fu.html
The competition between Amazon, Google and Microsoft around cloud computing is tough.
It is just a raw storage space (e.g. file system) added to EC2, you can use it as you prefer, for instance you can use it to allocate DBMS files. Obviously these storages are persistent, they remain usable after the termination of one EC2 instance.
The link with S3 and SimpleDB is not so clear, but for backup usage.
http://aws.typepad.com/aws/2008/04/block-to-the-fu.html
Subscribe to:
Posts (Atom)