The multi-master architecture enables active-active availability which allows zero downtime backend support. The current support is for MySQL compliant only.
Aurora Database now provides multiple reads/writes master instances across multiple Availability Zones. This makes all the database nodes in the cluster now accept read/write operations. This is different from the current support which allows to one node to be read/write and up to 15 replicas for ready-only.
The multi-master architecture enables active-active availability which allows zero downtime backend support. The current support is for MySQL compliant only.
0 Comments
Amazon Aurora database was announced in November 2014[1]. It is now a fully-managed, with both MySQL-compatible (in production July 2015) [5] and PostgreSQL-compatible (in production Oct 2017) , relational database engine hosted on Amazon RDS. This blog is a short analysis of this new cloud-based relational database. In summary, Aurora databases are:
Resources
Created 1/2/2017, Last Updated: 12/12/2017
According to Wikipedia [1], "the serverless compute is a cloud computing execution mode which the cloud provider dynamically manages the allocation of machine resources. ". Serverless compute has been around for some time. Amazon pioneered in the serverless with AWS Lambda. The current popular serverless databases includes Amazon DynamoDB, Microsoft Azure Data Lake, Microsoft Azure CosmosDB, Google Firebase and FaunaDB. Amazon Aurora Serverless was announced in AWS re:Invent 2017 [3], and it is now ready for preview. This blog briefly looks at the new serverless architecture. Serverless introduces a new software architecture. Serverless database means that database storage, scaling, high availability are now managed by the cloud provider. Users can just use WebService APIs for database services. The new architecture has the following benefits [2]:
Resources
AWS Aurora database [1][2] provides a production version compatible with PostgreSQL 9.6.1. Users can create a new Aurora database instance compatible with PosgreSQL 9.6.1. Resources Created 1/27/2017, Last Updated: 10/27/2017
The uses of the blockchain technology are not limited to Bitcoin or the Cryptocurrency. Blockchain can be used in many different use cases. Let's list some interesting ones. 1. Cryptocurrency Cryptocurrency is the most famous Cryptocurrency-Bitcoin. This is where the blockchain technology came from and where it becomes relevant to us. Cryptocurrency, like Bitcoin, allows users to directly send money without relying on the intermediary such as a bank. In this use case, each block is a transaction of money transfer. The ledger keeps track of the transaction history. Just heard the news that the Cryptocurrency market cap has passed $160 billions for the first time, as trading platforms post new records[1] The use case makes people adopting this technology more and more seriously. 2. Digital Asset Management Blockchain can help users trading assets. The assets can be learning credits, stock and others.
3. Smart Contract This use case focuses on contract part of the blockchain technology to execute contracts without intermediaries. Each block is a contact. The ledger keeps track of the contact history. Resources
A blockchain system (#blockchain) is a distributed database in a peer-to-peer network. Inside the blockchain system, the transactions are not processed by one computing system, but by many. The blockchain technology was first introduced in 2009, but it recently gained more attentions because of the bitcoin (#bitcoin), a digital cryptocurrency built on top of the blockchain technology. The new digital currency keeps reaching its record high price in 2017. The increasing adoption of the bitcoin makes people feel more confident in this technology. In this blog, I explore the technical details of this technology. Bitcoin is a worldwide cryptocurrency and digital payment system called the first decentralized digital currency. 1. What is the Blockchain? To understand the blockchain, you can think of it as a chain of blocks stored in a historical order.
2. How does the blockchain system run? A blockchain system runs based on a set of rules. These rules ensure the system completes transactions securely in public. In summary, blockchain defines a platform that:
The following are the details of the rules: 2.1 Transactions Have to be Signed To prevent the transaction forgery, each transaction has a unique ID and has to be signed by the sender. The sender creates a unique signature for each transaction using his private key. This is also known as the digital signature. The signature is then verified with the sender's public key. This can be represented as:
2.2 New Transaction Have to Reference Previous Transactions To prevent double spending or overspending, each transaction has to reference sender's transaction history to ensure the sender has enough amount (data) to complete the transactions. 2.3 Ledger Only Accepts Blocks with the Resolved "Proof of Work" and The Longest Blockchain Wins The blockchain creating the processing is a voting process shown as the following:
What is the Cryptographic Hash Function? A cryptographic hash function is a hash function which takes an input (or 'message') and returns a fixed-size alphanumeric string. The string is called the 'hash value', 'message digest', 'digital fingerprint', 'digest' or 'checksum'). (From Wikipedia) The puzzle resolving process can be described as:
2.4 Blocks Are Stored with Reference to the Previous One To maintain the correct order of block in the ledger, each block in the ledger has to refer to the block hash of the previous block to keep the ordering information. 3. Why would I use a blockchain system? There are some reasons to consider a blockchain system:
References
IBM Db2 12 for z/OS was announced 10/21/2016. "Db2 12 extends the core with new enhancements to scalability, reliability, efficiency, security, and availability. Db2 12 also empowers the next wave of applications in the cloud, mobile, and analytics spaces." [1]
Amazon RDS stands for Amazon Relational Database Service. It is a managed service which provides Web service interfaces for user to create, operate and manage relational databases. The current supported databases include:
Created 7/22/2015
IBM announced the i 7.2 on 4/28/2014 claiming "IBM i running on an IBM Power Systems server offers a highly scalable and virus-resistant architecture with a proven reputation for exceptional business resiliency." The key new features are:
Reference Created 5/8/2014
IBM DB2 for i is also called DB2 UDB for AS400, DB2 for iSeries etc. It's a relational database build into IBM i platform. IBM i platform one of the operating systems supported on IBM Power Systems alongside AIX and Linux and on IBM PureSystems alongside AIX, Linux and Windows. There are over 100,000 IBM i customer in 115 countries [2].
To understand DB2 for i, the followings are the key concepts:
Resources
Created 4/12/2014
|
Database ManagementNews and trend in database management Archives
December 2017
Categories |