November 18, 2010
0 Comments
You never develop code without version control, why do you develop your database without it?
Liquibase is an open source (Apache 2.0 Licensed), database-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes are stored in a human readable yet trackable form and checked into source control.
(Link: LiquiBase | Database Refactoring)
October 29, 2010
0 Comments
Teiid is comprised of tools, components and services for creating and executing bi-directional data services. Through abstraction and federation, data is accessed and integrated in real-time across distributed data sources without copying or otherwise moving data from its system of record.
(Link: Teiid is a data virtualization system that allows applications to use data from multiple, heterogenous data stores.)
October 21, 2010
0 Comments
Most of high scale web applications use MySQL + memcached. Many of them use also NoSQL like TokyoCabinet/Tyrant. In some cases people have dropped MySQL and have shifted to NoSQL. One of the biggest reasons for such a movement is that it is said that NoSQL performs better than MySQL for simple access patterns such as primary key lookups. Most of queries from web applications are simple so this seems like a reasonable decision.
(Link: Yoshinori Matsunobu’s blog: Using MySQL as a NoSQL – A story for exceeding 750,000 qps on a commodity server)
September 21, 2010
0 Comments
The Oracle database was back up by 1:12 Wednesday morning. But on Wednesday a second problem occurred, namely an overwhelming number of web requests. This turned out to be a cascade of retries in the face of – and of course exacerbating – poor response time.
(Link: Details of the JPMorgan Chase Oracle database outage)
August 23, 2010
0 Comments
In the mid-’90s, with the rise of larger Internet systems, these practices were revisited. At that time people began to consider the idea that availability was perhaps the most important property of these systems, but they were struggling with what it should be traded off against. Eric Brewer, systems professor at the University of California, Berkeley, and at that time head of Inktomi, brought the different trade-offs together in a keynote address to the PODC (Principles of Distributed Computing) conference in 2000.1 He presented the CAP theorem, which states that of three properties of shared-data systems—data consistency, system availability, and tolerance to network partition—only two can be achieved at any given time. A more formal confirmation can be found in a 2002 paper by Seth Gilbert and Nancy Lynch.4
(Link: Eventually Consistent – Revisited – All Things Distributed)
July 15, 2010
0 Comments
Strong statement, eh? The more I work with Mongo the more I am coming around to this way of thinking. I tell no lie when I say that I now approach Mongo with the same kind of excitement I first felt using Rails. For some, that may be enough, but for others, you probably require more than a feeling to check out a new technology.
1. Migrations are Dead
2. Single Collection Inheritance Gone Wild
3. Array Keys
4. Hash Keys
5. Embedding Custom Objects
6. Incrementing and Decrementing
7. Files, aka GridFS
(Link: Why I think Mongo is to Databases what Rails was to Frameworks // RailsTips by John Nunemaker)
May 8, 2010
0 Comments
Clustrix, a Y Combinator graduate from 2006, launched today with the claim that it’s built a transaction database with MySQL-like functionality and reliability that can scale to billions of entries. Clustrix plans to sell its appliance (which consists of more than a terabyte of memory and its proprietary software) to web firms that don’t want to take on the complicated task of sharding their data (replicating it across multiple databases), or moving to less robust database options like Cassandra or a key value store such as what’s provided by Twitter.
(Link: Clustrix Builds the Webscale Holy Grail: A Database That Scales)
April 27, 2010
0 Comments
Sequel provides thread safety, connection pooling and a concise DSL for constructing database queries and table schemas.
Sequel also includes a lightweight but comprehensive ORM layer for mapping records to Ruby objects and handling associated records.
Sequel supports advanced database features such as prepared statements, bound variables, stored procedures, master/slave configurations, and database sharding.
Sequel makes it easy to deal with multiple records without having to break your teeth on SQL.
Sequel currently has adapters for Amalgalite, ADO, DataObjects, DB2, DBI, Firebird, Informix, JDBC, MySQL, ODBC, OpenBase, Oracle, PostgreSQL and SQLite3.
(Link: Sequel: The Database Toolkit for Ruby)
February 24, 2010
0 Comments
Here at Carbon Five we have the luxury of working on many projects, so anything we can do to make things easier will pay off in multiplicity across new projects. One of the things that we have to deal with on every project is maintaining a database schema over time. We’ve had a manual process of capturing changes in incremental db patch scripts for a while, but it was error prone and sometimes neglected. We’ve been doing more Ruby on Rails work and found Rails Migrations easy to work with and a real time saver. We wanted something that would make our lives easier when working on Java projects in the same way Migrations improve Rails development. With that manifest in mind, Alon and I collaborated on a simple Java database migration framework.
(Link: Introducing Java DB Migrations)
February 21, 2010
0 Comments
# Sequel provides thread safety, connection pooling and a concise DSL for constructing database queries and table schemas.
# Sequel also includes a lightweight but comprehensive ORM layer for mapping records to Ruby objects and handling associated records.
# Sequel supports advanced database features such as prepared statements, bound variables, stored procedures, master/slave configurations, and database sharding.
# Sequel makes it easy to deal with multiple records without having to break your teeth on SQL.
# Sequel currently has adapters for ADO, Amalgalite, DataObjects, DB2, DBI, Firebird, Informix, JDBC, MySQL, ODBC, OpenBase, Oracle, PostgreSQL and SQLite3.
(Link: trafficbroker’s sequel at master – GitHub)
