Status of Software AG’s Tamino
Since I was researching Software AG anyway, I took the opportunity to ask about Software AG’s native XML DBMS Tamino, which certainly has some fans. Jim Fowler, Software AG’s Director of Market Development, Enterprise Transaction Systems, was kind enough to write up the following for me:
As you know, when Tamino was released in the late 1990s it was one of the first – if not the first – commercially available native XML database. We now have several hundred Tamino customers worldwide, and Software AG is fully committed to supporting our customers.
At the same time, we recognize that XML has matured and evolved in many different directions during the past decade; Read more
| Categories: Data types, Software AG, Structured documents | Leave a Comment |
Software AG – an Adablast from the Adapast
The two oldest major software products companies may well both be German – SAP and Software AG. They’re both a little older than CA (which, directly, or indirectly, has bought most of the other pioneers), Information Builders, or SAS, none of which – if I recall correctly – was founded before 1975-6.
In its current configuration, Software AG is based in Germany, publicly traded, and divided into two divisions:
- ETS (Enterprise Transaction Systems), perhaps better thought of as “Software AG Classic.” This is a 350 million Euros business, solidly profitable and still growing, albeit slowly.
- WebMethods, a SOA/integration division named after the biggest of the acquisitions it’s built from. This is a 100 million Euros business growing Very Fast.
The ETS folks briefed me last week. Highlights follow. I also posted about Software AG’s history over on Software Memories, which may provide some useful detail and context. Read more
| Categories: OLTP, Software AG | 3 Comments |
Netezza rolls out its compression story
The proximate cause for today’s flurry of Netezza-related posts is that the company has finally rolled out its compression story. In a nutshell, Netezza has developed its own version of columnar delta compression, slated to ship May, 2008. It compresses 2-5X, with the factor sometimes going up into double digits. Netezza estimates this produces a 2-3X improvement in overall performance, with the core marketing claim being that performance will “double” from compression alone. Read more
| Categories: Analytic technologies, Data warehouse appliances, Data warehousing, Database compression, Netezza, Theory and architecture | Leave a Comment |
ANALYTIC is the antonym of TRANSACTIONAL
In 1993, Ted Codd introduced the term OLAP (OnLine Analytic Processing) to describe data management that wasn’t optimized for OLTP (OnLine Transaction Processing). Later in the 1990s, Henry Morris of IDC introduced the term analytic applications to describe apps that weren’t transactional. Since then, no better word than “analytic” has emerged to cover the broad class of IT apps and technologies that aren’t focused on transactional processing.
In the latest incarnation, analytic appliances are coming to the fore. Read more
| Categories: Analytic technologies, Data warehouse appliances, Netezza, Vertica Systems | Leave a Comment |
Netezza is finally opening the kimono
I’ve bashed Netezza repeatedly for secrecy and obscurity about its technology and technical plans. Well, they’re getting a lot better. The latest post in a Netezza company blog, by marketing exec Phil Francisco, lays out their story clearly and concisely. And it’s backed up by a white paper that does more of the same. In particular, Page 11 of that white paper spells out possible future directions for enhancement, such as better compression, encryption, join filtering, and Netezza Developer Network stuff. Read more
The Netezza strategy for data shipping
I talked with Netezza today, and finally understand better why they don’t have node-to-node data shipping problems with only 1-gigabit (gigE) interconnects:
- Netezza boxes have lots of relatively small nodes, so all else being equal, each individual node has less communicating to do than, say, a DATAllegro node does.
- It’s not just just 1-gigabit. There’s a hierarchical communications architecture, and at one level in the hierarchy switches are talking to each other through 32 parallel 1-gigabit channels at a time.
| Categories: Data warehouse appliances, Netezza | Leave a Comment |
Just what does Oracle-compatibility mean?
Quite a bit of DBMS plug-compatibility is being claimed these days. Lewis Cunningham’s post on a few new EnterpriseDB features illustrates just how picky compatibility features can get. One can run Oracle code but not get around to handling comments properly? Sheesh.
| Categories: Emulation, transparency, portability, EnterpriseDB and Postgres Plus, Oracle | Leave a Comment |
A nice EnterpriseDB replacement of MySQL
I’m going to praise EnterpriseDB’s marketing communications twice in two blog posts, because I really liked some of the crunch they put into a press release announcing a MySQL replacement at FortiusOne. To wit (emphasis mine):
The PostGIS geospatial extensions to PostgreSQL played a key role in FortiusOne’s selection of EnterpriseDB Advanced Server, a PostgreSQL-based solution, and dramatically improved performance. FortiusOne needed to run complex spatial queries against large datasets quickly and efficiently, and found the MySQL spatial extensions to be far less complete and comprehensive than PostGIS. EnterpriseDB Advanced Server processes some of GeoCommons’ database-intensive rendering requests in one-thirtieth of the time required by MySQL. During peak loads, GeoCommons processes more than one hundred thousand complex requests per hour, requiring true enterprise-class performance and scalability.
Another major factor in FortiusOne’s replacement of MySQL with EnterpriseDB Advanced Server was the company’s need for advanced partitioning, custom triggers, and functional indexing. EnterpriseDB’s advanced partitioning capabilities instantly enabled linear performance, even with tables having billions of rows.
| Categories: Data types, EnterpriseDB and Postgres Plus, GIS and geospatial, MySQL | 10 Comments |
EnterpriseDB grows rapidly and fires its field sales force
Ashlee Vance discovered that EnterpriseDB had shot its field sales force, and opined that EnterpriseDB might generally be in trouble. EnterpriseDB CEO Andy Astor and marketing exec Derek Rodner responded quickly in their respective blogs. Andy and I also talked on the phone.
As best as I can tell, here’s what’s actually going on: Read more
| Categories: EnterpriseDB and Postgres Plus, Open source | 2 Comments |
Amazon Dynamo — when primary key access is enough
Amazon has a very decentralized technical operation. But even the individual pieces have interestingly huge scale. Thus, various different things they’re doing are of interest.
They recently presented a research paper on a high-performance transactional system called Dynamo. (Hat tip to Dare Obasanjo.) A key point is the following:
There are many services on Amazon’s platform that only need primary-key access to a data store. For many services, such as those that provide best seller lists, shopping carts, customer preferences, session management, sales rank, and product catalog, the common pattern of using a relational database would lead to inefficiencies and limit scale and availability. Dynamo provides a simple primary-key only interface to meet the requirements of these applications.
Now, I don’t think too many organizations past Amazon are going to decide that they can’t afford the overhead of an RDBMS for such OLTP-like applications. But I do think it will become increasingly common to find other reasons to eschew traditional OLTP relational architectures. Maybe you’ll want the schema flexibility of XML. Or perhaps you’ll be happy with a fixed relational schema, but will want to optimize for analytic performance.