Introduction_to_couchbase_server_tokyo_14

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
767
On Slideshare
459
From Embeds
308
Number of Embeds
3

Actions

Shares
Downloads
9
Comments
0
Likes
1

Embeds 308

http://www.couchbase.com 305
http://site-qa.cbauthx.com 2
http://localhost 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • All nodes are equal, single node type, easy to scale your cluster. No single point of failoverEvery node manages some active data and some replica data. Data is distributed across the clsuter and hence the load is also uniformly distributed using auto sharding. We have a fixed number of shards that a key get hashed to. 1024 shards, distributed across the cluster. Replication within the cluster for high availability. Number of replicas are configurable with upto 3 replicas. With auto-failiover or manual failover, replica information is immediately promoted to active Add multiple nodes at a time to grow and shrink your cluster.
  • JSON support – natively stored as json, whne you build an app, there is not conversion required. New doc viewing , editing capability. Indexing and querying – look inside your json, build views and query for a key, for ranges or to aggregate data Incremental mapreduce – powers indexing. Build complex views over your data. Great for real-time analytics XDCR – replicate information from one cluster to another cluster
  • 1.  A set request comes in from the application .2.  Couchbase Server responses back that they key is written3. Couchbase Server then Replicates the data out to memory in the other nodes4. At the same time it is put the data into a write que to be persisted to disk
  • 1.  A set request comes in from the application .2.  Couchbase Server responses back that they key is written3. Couchbase Server then Replicates the data out to memory in the other nodes4. At the same time it is put the data into a write que to be persisted to disk
  • 1.  A set request comes in from the application .2.  Couchbase Server responses back that they key is written3. Couchbase Server then Replicates the data out to memory in the other nodes4. At the same time it is put the data into a write que to be persisted to disk
  • 1.  A set request comes in from the application .2.  Couchbase Server responses back that they key is written3. Couchbase Server then Replicates the data out to memory in the other nodes4. At the same time it is put the data into a write que to be persisted to disk
  • CHANGE TRANSLATORBulletizethe text. Make sure the builds work.
  • Bulletize the text. Make sure build work properly.
  • Bulletize the text. Make sure build work properly.
  • Bulletize the text. Make sure the builds work.
  • Overview of what this feature is
  • 1.  A set request comes in from the application .2.  Couchbase Server responses back that they key is written3. Couchbase Server then Replicates the data out to memory in the other nodes4. At the same time it is put the data into a write que to be persisted to disk

Transcript

  • 1. Introduction to Couchbase Server Matt Ingenthron Director, Developer Solutions
  • 2. Couchbase Server NoSQL Document Database
  • 3. Couchbase Open Source Project • focused on distributed database technology and surrounding ecosystem 分散型データベースとエコシステムに 注力 • Supports both key-value and documentoriented use cases Key-valueとドキュメント指向のニーズをサ ポート • All components are available under the Apache 2.0 Public License Couchbase Open Source Project 全てのCouchbase製品はApache 2.0で公 開 • Obtained as packaged software in both enterprise and community editions. エンタープライズ版とコミュニティー版を 提供
  • 4. In this session • Overview of Couchbase Server features Couchbase Serverの特徴について • What’s new in Couchbase Server 2.1 and 2.2 Couchbase Server2.1から2.2のバージョンアップ情 報 • Architectural Overview and Couchbase Operations アーキテクチャの概要と各処理の解説 • Live Demo with a peak into new features ピーク時のデモ紹介と新機能について
  • 5. Couchbase Server Easy Scalability Consistent High Performance 常時1ミリ秒以下でデータ の読込み/書込みを行う アプリケーションの変更やダウ ンタイム伴わず、クリックをす るだけでサーバの追加が可能 Always On 24x365 ソフトウェアとハードウェアの アップグレードやメンテナンス 時にダウンタイムを必要としな い JSON JSON JSO JSON JSON N Flexible Data Model データベース構築時にスキー マ定義を必要としないJSON ドキュメントモデル
  • 6. Core Couchbase Server Features Built-in clustering – All nodes equal Append-only storage layer マスタのノードを必要としないクラス追記専用のストレージ層 タ Data replication with auto-failover Online compaction データを複製し、自動フェイル オーバーが可能 システムを停止せずにデータ を最適化 Zero-downtime maintenance Monitoring and admin API & UI メンテナンス時にダウンタイム を必要としない 監視および管理用のAPIとUI を提供 Built-in managed cache SDK for a variety of languages 組み込み式のキャッシュ さまざまな言語向けのSDKを サポート
  • 7. 2.0 introduced JSON support JSONサポート Indexing and Querying インデックスと検索機 能 JSON JSON JSO JSON N JSON Incremental Map Reduce インクリメンタル MapReduce Cross data center replication XDCR(クロスデータセンタレプリケー ション)
  • 8. Learn more about in the New in 2.2 2.1 introduced the health checkerCouchbase [SF] “Keeping your cluster healthy” session from  Multi-threaded persistence engine マルチスレッドの永続化エンジン  Optimistic XDCR XDCR(クラスタ間のレプリケーショ ン)  CBHealthcheck – Cluster health check tool クラスタのヘルスチェック機能  Hostname management ホスト名の管理  Rebalance progress indicators リバランスの進捗状況表示  New XDCR protocol based on memcached MemcachedベースのXDCRプロトコー ル  Read-only admin user 閲覧専用の管理ユーザの機能を追加  Automated and optimized purge management データの自動最適化機能  CBRecovery Data recovery tool from remote clusters リモート操作によるデータの復元機能  Non-root, non-sudo install システム管理者権限なしでインス トール可能
  • 9. Couchbase Server Architecture 11211 11210 Query API Memcapable 1.0 Memcapable 2.0 New Persistence Layer vBucket state and replication manager Node health monitor Rebalance orchestrator storage interface Global singleton supervisor Data Manager Configuration manager Couchbase EP Engine Process monitor Memcached Heartbeat Moxi REST management API/Web UI Query Engine 8092 Cluster Manager http on each node one per cluster Erlang/OTP HTTP Erlang port mapper Distributed Erlang 8091 4369 21100 - 21199
  • 10. Couchbase Server Architecture Query Engine Query API 11210 / 11211 8091 Admin Console Data access ports http Object-managed Cache Erlang /OTP 8092 REST management API/Web UI Replication, Rebalance, Shard State Manager Multi-threaded Persistence Engine Data Manager Cluster Manager
  • 11. Couchbase Operations
  • 12. Single node - Couchbase Write Operation Doc 1 App Server Couchbase Server Node 3 2 Managed Cache Replication Queue Disk Doc 1 Disk Queue To other node 3
  • 13. Single node - Couchbase Update Operation Doc 1’ App Server Couchbase Server Node 3 2 Managed Cache Replication Queue 1 Doc 1’ Disk Queue To other node 3 Disk Doc 1
  • 14. GET Doc 1 Single node - Couchbase Read Operation App Server Couchbase Server Node 3 2 Managed Cache Replication Queue Doc 1 Disk Queue To other node 3 Disk Doc 1
  • 15. Single node – Couchbase Cache Miss GET Doc 1 2 App Server 3 2 Managed Cache Replication Queue Doc 5 4 4 Doc Doc Doc 1 Doc Doc 3 2 Disk Queue To other node Disk Doc 1 Doc 6 Doc 5 Doc 4 Doc 3 3 Doc 2 Couchbase Server Node
  • 16. Basic Operation APP SERVER 1 • Docs distributed evenly across servers APP SERVER 2 COUCHBASE Client Library COUCHBASE Client Library CLUSTER MAP CLUSTER MAP • ドキュメントはサーバ間に均等に分散配置さ れる Each server stores both active and replica docs (Only one server active at a time) 各サーバは、アクティブとレプリカのドキュメ ントの両方を格納 (データは1つのサーバのみアク READ/WRITE/UPDATE ティブ) SERVER 1 SERVER 2 SERVER 3 ACTIVE ACTIVE ACTIVE Doc 5 Doc Doc 4 Doc Doc 1 Doc Doc 2 Doc Doc 7 Doc Doc 2 Doc Doc 9 Doc Doc 8 Doc Doc 6 Doc REPLICA REPLICA REPLICA Doc 4 Doc Doc 6 Doc Doc 7 Doc Doc 1 Doc Doc 3 Doc Doc 9 Doc Doc 8 Doc Doc 2 Doc Doc 5 Doc COUCHBASE SERVER CLUSTER User Configured Replica Count = 1 • Client library provides app with simple interface to database クライアントライブラリはシンプルなインター フェースを提供 • Cluster map provides map to which server doc is on (App never needs to know) クラスタマップはどのサーバのドキュメントが アクティブ状態であるかを示す • App reads, writes, updates docs アプリケーションはドキュメントの読込み、書 込み、アップデートを行う • Multiple app servers can access same document at same time 各サーバは同時に同じドキュメ ントにアクセスすることが可能
  • 17. Add Nodes to Cluster APP SERVER 1 COUCHBASE Client Library COUCHBASE Client Library CLUSTER MAP • Two servers added One-click operation APP SERVER 2 CLUSTER MAP READ/WRITE/UPDATE たった1回のクリックで サーバ2台を簡単に追加 READ/WRITE/UPDATE SERVER 1 SERVER 2 SERVER 3 SERVER 4 SERVER 5 ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE • Docs automatically rebalanced across cluster (Even distribution of docs Minimum doc movement) Doc 5 Doc Doc 4 Doc Doc 1 Doc ドキュメントはクラスタ内 で自動的に再配置される Doc 2 Doc Doc 7 Doc Doc 2 Doc • Cluster map updated Doc 9 Doc Doc 8 Doc Doc 6 Doc REPLICA REPLICA REPLICA Doc 4 Doc Doc 6 Doc Doc 7 Doc Doc 1 Doc Doc 3 Doc Doc 9 Doc Doc 8 Doc Doc 2 Doc Doc 5 Doc COUCHBASE SERVER CLUSTER User Configured Replica Count = 1 クラスタマップのアップ デート REPLICA REPLICA • App database calls now distributed over larger number of servers アプリケーションは意識す ることなく、追加したサー バに再配置されたデータに アクセス可能
  • 18. Learn more about running “Couchbase in production” Fail Over Node in Perry’s session at 15:15 APP SERVER 1 COUCHBASE Client Library COUCHBASE Client Library CLUSTER MAP • App servers accessing docs APP SERVER 2 CLUSTER MAP アプリケーションサーバが ドキュメントにアクセス • Requests to Server 3 fail サーバ3がダウン SERVER 1 SERVER 2 SERVER 3 SERVER 4 SERVER 5 ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE Doc 5 Doc 2 Doc Doc Doc 1 Doc 4 Doc 7 Doc Doc Doc 1 Doc 2 Doc Doc Doc 9 Doc 8 Doc Doc 6 Doc Doc Doc Doc 3 REPLICA Promotes replicas of docs to active Updates cluster map クラスタがサーバダウンを 検知(レプリカをアクティブ に昇格) REPLICA REPLICA REPLICA Doc 4 Doc Doc 6 Doc Doc 7 Doc Doc 5 Doc 1 Doc Doc 3 Doc Doc 9 Doc Doc 2 COUCHBASE SERVER CLUSTER User Configured Replica Count = 1 • Cluster detects server failed Doc REPLICA Doc 8 Doc Doc • Requests for docs now go to appropriate server ドキュメントをアプリケーショ ンに送る • Typically rebalance would follow 通常はその後リバランスがされ る
  • 19. Demo Time
  • 20. Indexing and Querying APP SERVER 1 • Indexing work is distributed amongst nodes APP SERVER 2 COUCHBASE Client Library COUCHBASE Client Library CLUSTER MAP CLUSTER MAP インデックスは全てのノード間 に渡って行われる • Large data set possible Query SERVER 1 SERVER 2 ACTIVE ACTIVE SERVER 3 ACTIVE Doc 5 Doc Doc 5 Doc Doc 5 Doc Doc 2 Doc Doc 2 Doc Doc 2 Doc Doc 9 Doc Doc 9 Doc • Parallelize the effort Doc Doc 9 大規模なデータセットが可能 REPLICA 並列処理する REPLICA REPLICA Doc 4 Doc Doc 4 Doc Doc 4 Doc Doc 1 Doc Doc 1 Doc Doc 1 Doc Doc 8 Doc Doc 8 Doc Doc 8 Doc COUCHBASE SERVER CLUSTER User Configured Replica Count = 1 • Each node has index for data stored on it 各ノードは格納されているデー タのインデックスを保持する • Queries combine the results from required nodes クエリはリクエストが送られた ノードの集合体に対し、 その結果を集計する
  • 21. Cross data center replication – Data flow 2 Doc 1 App Server Couchbase Server Node 3 2 Managed Cache Replication Queue Doc 1 Disk Queue To other node 3 Disk Doc 1 XDCR Engine To other cluster
  • 22. Cross Data Center Replication (XDCR) Optimistic replication Couchbase Server – San Francisco SERVER 1 SERVER 2 SERVER 3 Per replication Tunable Parameters Couchbase Server – New York SERVER 1 SERVER 2 Optimized protocol based on memcached Reliability and performance at scale SERVER 3
  • 23. Demo Time
  • 24. What’s else is New?
  • 25. Learn more about N1QL at Couchbase Query Language query.couchbase.com N1QL ニッケル (SQLライクなクエリ言 語) Read “Nickel” Our next generation query language for JSON In Dev Preview
  • 26. Couchbase Server www.couchbase.com/download
  • 27. Thank you! matt@couchbase.com @ingenthr Download Couchbase Server 2.2 http://www.couchbase.com/download