 Your new post is loading...
Your new post is loading...
|
Scooped by
Mickael Ruau
August 19, 2013 8:15 AM
|
Oracle sort la version 6 de l'outil MySQL Workbench. L'éditeur annonce de nombreuses améliorations et nouveautés : interface, développement, design, nouveaux outils...
le designer de bases de données (OS X)
L'outil permet de créer, gérer,...
|
|
Scooped by
Mickael Ruau
August 18, 2013 5:52 PM
|
Les données en double sont déjà difficiles à contrôler manuellement dans les petits fichiers, donc avec les grandes quantités de données telles que celles gérées avec MySQL, ils ne peuvent être maîtrisés qu'avec un outil approprié.
|
|
Scooped by
Mickael Ruau
August 14, 2013 10:36 AM
|
La prise en considération croissante des données non structurées et l’essor des données en ligne concourent ainsi à une véritable explosion du volume des données. Mais au-delà du simple aspect quantitatif de leur gestion, il convient de leur donner du sens et de s’intéresser autant à la qualité intrinsèque qu’aux usages qui en sont faits.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:49 PM
|
Introduction We’ve entered an era of application development that increasingly requires scalable solutions to everyday problems. By and large, the methods used to scale an application to massive proportions are fairly standardized.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:49 PM
|
Sharding Architectures International PHP Conference 2008
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:47 PM
|
Cloud computing offerings differ in depth, breadth, style, and fine print; beneath the heady metaphor lurk familiar pitfalls, complex pricing, and many questions
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:47 PM
|
One interesting trend that I've noticed in many of the organizations that I've been into is that increasingly databases are being built to serve single applications. The early visions of databases shared amongst multiple applications is no longer the first choice.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:44 PM
|
CodeFutures supplies database performance tools based on database sharding, Data Access Objects, and Java Persistence Architecture. The benefits are higher developer productivity, better software quality, and lower maintenance costs.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:44 PM
|
CodeFutures supplies database performance tools based on database sharding, Data Access Objects, and Java Persistence Architecture. The benefits are higher developer productivity, better software quality, and lower maintenance costs.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:44 PM
|
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:43 PM
|
Update 4: Why you don’t want to shard. by Morgon on the MySQL Performance Blog. Optimize...
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:41 PM
|
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:40 PM
|
A partition is a division of a logical database or its constituting elements into distinct independent parts. Database partitioning is normally done for manageability, performance or availability reasons.
A popular and favourable application of partitioning is in a distributed database management system. Each partition may be spread over multiple nodes, and users at the node can perform local transactions on the partition. This increases performance for sites that have regular transactions involving certain views of data, whilst maintaining availability and security.
Current high end relational database management systems provide for different criteria to split the database. They take a partitioning key and assign a partition based on certain criteria. Common criteria are:
|
|
|
Scooped by
Mickael Ruau
August 18, 2013 5:55 PM
|
|
|
Scooped by
Mickael Ruau
August 18, 2013 5:51 PM
|
Il arrive souvent que les listes d'adresses utilisées pour les campagnes de marketing direct soient composées de différentes sources.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:51 PM
|
I recently received a great comment, in the form of a question, on the Scalability Strategies Primer: Database Sharding post. I thought the answer to Yuriy’s comment deserved its own post so that I could get as detailed as possible...
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:49 PM
|
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:48 PM
|
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:47 PM
|
No, not SHARED lessons, I mean SHARD lessons. I have to admit that until about a year ago I didn't really know the term shards in relation to databases. Now don't confuse that with not understanding how databases can be...
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:46 PM
|
I've already written about the fact that databases are increasingly being created to support a single application and Michael Stonebraker has written about the drivers for multiple types of database engines. However, these trends extend much deeper than that.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:44 PM
|
CodeFutures supplies database performance tools based on database sharding, Data Access Objects, and Java Persistence Architecture. The benefits are higher developer productivity, better software quality, and lower maintenance costs.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:44 PM
|
CodeFutures supplies database performance tools based on database sharding, Data Access Objects, and Java Persistence Architecture. The benefits are higher developer productivity, better software quality, and lower maintenance costs.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:43 PM
|
Hardware Layouts for LAMP Installations John Allspaw, Flickr Plumbr Flickr (Yahoo) [email_address] October 18, 2005
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:42 PM
|
Le sharding ou partitionnement de données entre dans le cadre plus global de la scalabilité. Il s’agit tout simplement du découpage des données d’une base afin d’avoir à requêter sur moins d’occurrences et donc d’avoir un résultat plus rapide donc de meilleures performances. Le sharding est une solution à part entière, mais qui ne convient pas dans tous les cas. Nous verrons également quelles sont les solutions alternatives pour une amélioration des temps de réponse au niveau d’une base de données.
|
|
Scooped by
Mickael Ruau
August 12, 2013 9:40 PM
|
A database shard is a horizontal partition in a database or search engine. Each individual partition is referred to as a shard or database shard.
Horizontal partitioning is a database design principle whereby rows of a database table are held separately, rather than being split into columns (which is what normalization and vertical partitioning do, to differing extents). Each partition forms part of a shard, which may in turn be located on a separate database server or physical location.
There are numerous advantages to this partitioning approach. Since the tables are divided and distributed into multiple servers, the total number of rows in each table in each database is reduced. This reduces index size, which generally improves search performance. A database shard can be placed on separate hardware, and multiple shards can be placed on multiple machines. This enables a distribution of the database over a large number of machines, which means that the database performance can be spread out over multiple machines, greatly improving performance. In addition, if the database shard is based on some real-world segmentation of the data (e.g., European customers v. American customers) then it may be possible to infer the appropriate shard membership easily and automatically, and query only the relevant shard.[1]
|
Scoop.it!
