The final version of the Object-Relational Mapping, ORM framework Hibernate 4.3 was recently released and is now a certified implementation of the JPA 2.1 specification, (JSR 338), released in May 2013.
With Facebook recently releasing Presto as open source, the already crowded SQL-in-Hadoop market just became a tad more intricate. A number of open source tools are competing for the attention of developers: Hortonworks Stinger initiative around Hive, Apache Drill, Apache Tajo, Cloudera’s Impala, Salesforce’s Phoenix (for HBase) and now Facebook’s Presto.
Opserver is an open source monitoring solution, released by StackExchange, of StackOverflow's fame. Opserver provides a quick overall view of each monitored system's health, while allowing the user to deep dive using a drill-down approach. InfoQ talked with Nick Crave, one of Opserver’s creators, for additional insight.
New version of Cascading released this week incorporates Hadoop 2 support and includes Cascading Lingual - an open source project that provides a comprehensive ANSI SQL interface for accessing Hadoop-based data
Amazon RDS adds PostgreSQL to the list of databases supported by the service. The launch supports Postgres version 9.3.1 with plans to support new versions as they become available.
Facebook has open-sourced Presto, their distributed SQL query engine. Presto uses a pipelined architecture rather than the Map/Reduce design found elsewhere. In production since early this year, Facebook has since “deployed in multiple geographical regions and [they] have successfully scaled a single cluster to 1,000 nodes”.
New database developments indicate a return to SQL, but not by running the traditional relational stores on bigger and better hardware, not even on sharded architectures, but through NewSQL solutions.
NuoDB has announced version 2.0 of their NewSQL database, now a globally distributed database that can run in the cloud or on premises with real-time replication.
One of the biggest challenges when researching a new technology is determining where to start. A typical SQL Server installation could easily have hundreds of tables. Examining each one by hand to determine which would benefit from conversion, is a daunting challenge. This is where the AMR Tool comes into play.
In this report we look at the internals of SQL Server’s In-Memory OLTP to see how it uses timestamp-like transaction ids in lieu of locks.
SQL Server 2014 will offer Clustered Columnstore Indexes. These will offer the performance and compression benefits of column-oriented storage without the need to restrict the underlying table to read-only access.
Originally this report was titled “Natively Compiled Queries”, but that doesn’t do justice to how deep this runs. When a memory optimized table is created, SQL Server will create a DLL specifically for that table. All data access for the table, including indexes, occurs through this DLL.
SQL Server 2014’s Memory Optimized Tables handle indexes very differently than traditional tables. First and foremost, you must have at least one index and cannot have more than eight indexes. Only the primary key can be marked as unique and don’t even think about foreign keys or filtered indexes.
In SQL Server 2014 Microsoft will be unveiling its lock-free technology known as Memory Optimized Tables. Using a new storage and query subsystem, these represent a radical departure from traditional database design.
PostgreSQL 9.3 comes with Fast Fail-over and streaming-only Remastering as well as many developer-focussed features such as materialized views, auto-updateable views, many features for JSON data-type and more.