apache-ignite
42 строки · 2.5 Кб
1// Licensed to the Apache Software Foundation (ASF) under one or more
2// contributor license agreements. See the NOTICE file distributed with
3// this work for additional information regarding copyright ownership.
4// The ASF licenses this file to You under the Apache License, Version 2.0
5// (the "License"); you may not use this file except in compliance with
6// the License. You may obtain a copy of the License at
7//
8// http://www.apache.org/licenses/LICENSE-2.0
9//
10// Unless required by applicable law or agreed to in writing, software
11// distributed under the License is distributed on an "AS IS" BASIS,
12// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13// See the License for the specific language governing permissions and
14// limitations under the License.
15Ignite clients come in several different flavors, each with various capabilities.
16link:SQL/JDBC/jdbc-driver[JDBC] and link:SQL/ODBC/odbc-driver[ODBC] drivers
17are useful for SQL-only applications and SQL-based tools. Thick and thin clients go beyond SQL capabilities and
18support many more APIs. Finally, ORM frameworks like Spring Data or Hibernate are also integrated with Ignite and
19can be used as an access point to your cluster.
20
21Let's review the difference between thick and thin clients by comparing their capabilities.
22
23*Thick* clients (client nodes) join the cluster via an internal protocol, receive all of the cluster-wide
24updates such as topology changes, are aware of data distribution, and can direct a query/operation to a server node
25that owns a required data set. Plus, thick clients support all of the Ignite APIs.
26
27*Thin* clients (aka. lightweight clients) connect to the cluster via binary protocol with a well-defined
28message format. This type of client supports a limited set of APIs (presently, key-value and SQL operations only) but
29in return:
30
31- Makes it easy to enable programming language support for Ignite. Java, .NET, C++, Python, Node.JS, and
32PHP are supported out of the box.
33
34- Doesn't have any dependencies on JVM. For instance, .NET and C++ _thick_ clients have a richer feature set but
35start and use JVM internally.
36
37- Requires at least one port opened on the cluster end. Note that more ports need to be opened if
38partition-awareness is used for a thin client.
39
40TIP: The ODBC driver uses a protocol similar to the thin client's. As for the JDBC driver, it comes in two flavors -
41a thick version of the driver that utilizes a Java thick client internally and a thin counterpart, based on the thin
42client's protocol.
43