Modified: ignite/site/trunk/features/datagrid.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/features/datagrid.html (original) +++ ignite/site/trunk/features/datagrid.html Tue Mar 1 02:05:20 2016 @@ -299,16 +299,23 @@ under the License. Ignite also allows to configure multiple <b>backup copies</b> to guarantee data resiliency in case of failures. </p> - <p> - Regardless of which caching mode is used, Ignite guarantees data consistency - across all cluster members, regardless of various failure conditions. - </p> <div class="page-links"> <a href="http://apacheignite.readme.io/docs/cache-modes"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> + <td class="left">Collocated Processing</td> + <td> + <p> + Ignite allows executing any native Java, C++, and .NET/C# code directly on the server-side, close to the data, in collocated fashion. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/affinity-collocation"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> <td class="left">Self-Healing Cluster</td> <td> <p> @@ -325,129 +332,271 @@ under the License. <td class="left">Client-side Near Caches</td> <td> <p> - Whenever the data is accessed from remote clients, Ignite also supports client-side - <code>NEAR Caching</code>. In <i>transactional</i> mode, the data stored in NEAR caches is also - transactional and is either automatically updated or invalidated in consistent fashion - update transaction commit. + Near cache is local client-side cache that stores the most recently and most frequently accessed data. </p> + <div class="page-links"> + <a href="http://apacheignite.readme.io/docs/near-caches"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Off-Heap and On-Heap Memory</td> + <td> <p> - Regardless of which caching mode is used, Ignite guarantees data consistency - across all cluster members, regardless of various failure conditions. + Ignite supports 2 modes for caching data in-memory: + <span style="white-space: nowrap"><code>off-heap</code></span> and + <span style="white-space: nowrap"><code>on-heap</code></span>. + Off-Heap memory allows your cache to overcome lengthy JVM Garbage Collection (GC) pauses + when working with large heap sizes by caching data outside of main Java Heap space, + but still in RAM. </p> <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/near-caches"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <a href="http://apacheignite.readme.io/docs/off-heap-memory"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> - <td class="left">ACID Transactions</td> + <td class="left">Off-Heap Indexes</td> <td> <p> - Ignite supports 2 modes for cache operation, <i>transactional</i> and <i>atomic</i>. - In <i>transactional</i> mode you are able to group multiple cache operations in a - transaction, while <i>atomic</i> mode supports multiple atomic operations, one at a time. - <i>Atomic</i> mode is more light-weight and generally has better performance over - transactional caches. + Whenever off-heap memory is configured, Ignite will also store query indexes off-heap + as well. This means that indexes will not take any portion of on-heap memory. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/off-heap-memory"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Tiered Storage</td> + <td> + <p> + As data gets colder (not accessed) Ignite will optionally migrate it + from On-Heap memory to Off-Heap memory, and from Off-Heap memory to Swap (disk) storage. </p> <p> - In <i>transactional</i> mode Ignite supports <code>OPTIMISTIC</code> and - <code>PESSIMISTIC</code> transactions and utilizes 2PC protocol with many - <i>one-phase-commit</i> optimizations whenever applicable. + Whenever some data is accessed, it will immediately be propagated to the top tier + pushing some other colder data down the next memory tier. </p> <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/transactions"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <a href="http://apacheignite.readme.io/docs/off-heap-memory"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> - <td class="left">Queries & Distributed Joins</td> + <td class="left">Binary Protocol</td> <td> <p> - Ignite supports a very elegant query API with support for: - <ul class="page-list"> - <li>Scan Queries (Predicate-based)</li> - <li>SQL Queries (ANSI 99)</li> - <li>Text Queries</li> - </ul> + Starting from v1.5 Ignite introduced a new concept of storing data in caches, called BinaryObjects. It allows you to: </p> + <ul class="page-list"> + <li>Read a serialized object's field without full object deserialization.</li> + <li>Dynamically change an object's structure.</li> + <li>Dynamically create an object.</li> + </ul> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/jcache"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">ACID Transactions</td> + <td> <p> - For <code>SQL</code> and <code>TEXT</code> queries ignites supports in-memory indexing, so all the data lookups are extremely fast. - If you are caching your data in off-heap memory, then query indexes will also be cached in off-heap memory as well. - </p> + Ignite provides fully ACID compliant distributed transactions that ensure guaranteed consistency.</p> <p> - Ignite also allows users to implement their own custom indexing using pluggable - <code>IndexingSpi</code>. + Ignite supports <code>OPTIMISTIC</code> and <code>PESSIMISTIC</code> concurrency modes + as well as <code>READ_COMMITTED</code>, <code>REPEATABLE_READ</code>, and <code>SERIALIZABLE</code> isolation levels.</p> + <p> + Ignite transactions utilize 2PC protocol with many one-phase-commit optimizations whenever applicable. </p> <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/cache-queries"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <a href="http://apacheignite.readme.io/docs/transactions"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> - <td class="left">Continuous Queries</td> + <td class="left" width="35%">Deadlock-Free Transactions</td> <td> <p> - Continuous queries are useful for cases when you want to execute a query and then - continue to get notified about the data changes that fall into your query filter. + Ignite supports deadlock-free, optimistic transactions, which do not acquire any locks, and free users from worrying about the lock order. Such transactions also provide much better performance. </p> - <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/continuous-queries"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/transactions"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> - <td class="left">Off-Heap and On-Heap Memory</td> + <td class="left" width="35%">Transactional Entry Processor</td> <td> <p> - Ignite supports 2 modes for caching data in-memory: - <span style="white-space: nowrap"><code>off-heap</code></span> and - <span style="white-space: nowrap"><code>on-heap</code></span>. - Off-Heap memory allows your cache to overcome lengthy JVM Garbage Collection (GC) pauses - when working with large heap sizes by caching data outside of main Java Heap space, - but still in RAM. + Ignite transactional entry processor allows executing collocated user logic on the server side within a transaction. </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/affinity-collocation#ignitecompute-vs-entryprocessor"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left" width="35%">Cross-Partition Transactions</td> + <td> <p> - Whenever off-heap memory is configured, Ignite will also store query indexes off-heap - as well. This means that indexes will not take any portion of on-heap memory. + In Ignite, transactions can be performed on all partitions of a cache across the whole cluster. </p> - <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/off-heap-memory"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/transactions#ignitetransactions"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> - <td class="left">Tiered Memory</td> + <td class="left" width="35%">Locks</td> <td> <p> - As data gets colder (not accessed) Ignite will optionally migrate it - from On-Heap memory to Off-Heap memory, and from Off-Heap memory to Swap (disk) storage. + Ignite allows developers to define explicit locks enforcing mutual exclusion on cached objects. </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/locks"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">SQL Queries</td> + <td> <p> - Whenever some data is accessed, it will immediately be propagated to the top tier - pushing some other colder data down the next memory tier. + Ignite supports the standard SQL syntax (ANSI 99) to query the cache. You can use any SQL function, aggregation, or grouping. </p> <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/off-heap-memory"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + <a href="https://apacheignite.readme.io/docs/sql-queries"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left" width="35%">Distributed Joins</td> + <td> + <p> + Ignite supports <b>distributed SQL joins</b> as well as <b>cross-cache joins</b>. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/sql-queries#sql-joins"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> + <td class="left" width="35%">Continuous Queries</td> + <td> + <p> + Continuous queries are useful for cases when you want to execute a query and then continue to get notified about the data changes that fall into your query filter. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/continuous-queries"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left" width="35%">Query Indexing</td> + <td> + <p> + For SQL queries, ignites supports in-memory indexing, so all the data lookups are extremely fast. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/sql-queries#configuring-sql-indexes-using-annotations"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left" width="35%">Query Consistency</td> + <td> + <p> + In Ignite, provides full query consistency. Updates that happened after the query execution started do not affect the query result. + </p> + </td> + </tr> + <tr> + <td class="left" width="35%">Query Fault-Tolerance</td> + <td> + <p> + Ignite queries are fault-tolerant, i.e. query result is always consistent and is not affected by cluster topology changes. + </p> + </td> + </tr> + <tr> <td class="left">JDBC Driver</td> <td> <p> Ignite is shipped with <code>JDBC Driver</code> that allows you to retrieve distributed data from cache using standard SQL queries and JDBC API. </p> - <p> - JDBC driver allows users to connect to Ignite using any standard SQL tool and start - executing SQL queries against the in-memory data stored in Ignite caches. - </p> <div class="page-links"> <a href="http://apacheignite.readme.io/docs/jdbc-driver"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> <tr> + <td class="left">ODBC Driver</td> + <td> + <p> + Ignite ODBC driver allows users to retrieve data from cache using standard SQL queries and ODBC API. + </p> + </td> + </tr> + <tr> + <td class="left" width="35%">Write-Through</td> + <td> + <p> + Write-Through mode allows updating the data in the database. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/persistent-store"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Read-Through</td> + <td> + <p> + Read-Through mode allows reading the data from the database. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/persistent-store"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Write-Behind Caching</td> + <td> + <p> + Ignite provides an option to asynchronously perform updates to the database via Write-Behind Caching. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/persistent-store#write-behind-caching"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Automatic Persistence</td> + <td> + <p> + Automatically connect to the underlying database and generate XML OR-mapping configuration and Java domain model POJOs. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/automatic-persistence"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left"> + <b>Database Integration</b> + </td> + <td> + <p> + Ignite can automatically integrate with external databases - RDBMS, NoSQL, and HDFS. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/persistent-store"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> <td class="left">Web Session Clustering</td> <td> <p> @@ -490,6 +639,26 @@ under the License. </div> </td> </tr> + <tr> + <td class="left">XA/JTA</td> + <td> + <p> + Ignite can be configured with a Java Transaction API (JTA) transaction manager lookup class. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/transactions#integration-with-jta"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">OSGI Support</td> + <td> + <p></p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/osgi-starting-inside-a-container"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> </tbody> </table> </section>
Modified: ignite/site/trunk/features/datastructures.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/datastructures.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/features/datastructures.html (original) +++ ignite/site/trunk/features/datastructures.html Tue Mar 1 02:05:20 2016 @@ -190,6 +190,17 @@ under the License. </thead> <tbody> <tr> + <td class="left">Queue and Set</td> + <td> + <p> + Ignite provides an implementation of a fast <b>Distributed Blocking Queue</b> and <b>Distributed Set</b>. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/queue-and-set"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> <td class="left">Collocated vs. Non-Collocated</td> <td> <p> @@ -218,6 +229,28 @@ under the License. </td> </tr> <tr> + <td class="left">Atomic Types</td> + <td> + <p> + Ignite supports distributed <b>AtomicLong</b> and <b>AtomicReference</b>. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/atomic-types"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">CountDownLatch</td> + <td> + <p> + Ignite CountDownLatch allows you to synchronize jobs on all Ignite nodes. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/countdownlatch"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> <td class="left">Reservation-based ID Generator</td> <td> <p> @@ -226,15 +259,22 @@ under the License. the data structure reserves ahead a range of values, which are guaranteed to be unique across the cluster for this sequence instance. </p> - <p> - Until all the values in the reservation are used, all sequence increment operations - will happen locally on the client. - </p> <div class="page-links"> <a href="http://apacheignite.readme.io/docs/id-generator"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> </div> </td> </tr> + <tr> + <td class="left">Semaphore</td> + <td> + <p> + Ignite's distributed semaphore implementation and behavior is similar to <b>java.util.concurrent.Semaphore</b>. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/distributed-semaphore"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> </tbody> </table> </section> Modified: ignite/site/trunk/features/deploy.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/deploy.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/features/deploy.html (original) +++ ignite/site/trunk/features/deploy.html Tue Mar 1 02:05:20 2016 @@ -94,6 +94,28 @@ under the License. </tr> </thead> <tbody> + <tr> + <td class="left">Zero Deployment</td> + <td> + <p> + Ignite nodes automatically become aware of custom classes, eliminating the need to explicitly deploy them. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/zero-deployment"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Dynamic Schema Changes</td> + <td> + <p> + Ignite stores objects in binary format eliminating the need to deploy classes on server nodes. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/binary-marshaller"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> <tr> <td class="left">Stand-Alone Clusters</td> <td> @@ -161,6 +183,15 @@ under the License. </div> </td> </tr> + <tr> + <td class="left">OSGI Support</td> + <td> + <p></p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/osgi-starting-inside-a-container"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> </tbody> </table> </section> Modified: ignite/site/trunk/features/messaging.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/messaging.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/features/messaging.html (original) +++ ignite/site/trunk/features/messaging.html Tue Mar 1 02:05:20 2016 @@ -51,19 +51,28 @@ under the License. <main id="main" role="main" class="container"> <section id="messaging" class="page-section"> - <h2 class="first">Distributed Messaging</h2> + <h2 class="first">Distributed Messaging & Events</h2> <p> - Apache Ignite provides high-performance cluster-wide messaging functionality to exchange data via - publish-subscribe and direct point-to-point communication models. Messages can be exchanged in + Ignite provides <b>high-performance cluster-wide messaging</b> functionality to exchange data via + publish-subscribe and direct point-to-point communication models. Messages can be exchanged in an ordered or unordered fashion. Ordered messages are slightly slower, but when used, Ignite guarantees that messages will be received in the same order they were sent. </p> + + <p> + Ignite <b>distributed events</b> functionality allows applications to receive notifications when a variety + of events occur in the distributed grid environment. You can automatically get notified for task executions, + read, write or query operations occurring on local or remote nodes within the cluster. + Event notifications can also be grouped together and sent in batches or timely intervals. + </p> <div class="code-examples"> <div class="page-heading">Code Examples:</div> <!-- Nav tabs --> <ul id="messaging-examples" class="nav nav-tabs"> <li class="active"><a href="#messaging-example-ordered" aria-controls="home" data-toggle="tab">Ordered Messaging</a></li> <li><a href="#messaging-example-unordered" aria-controls="profile" data-toggle="tab">Unordered Messaging</a></li> + <li><a href="#events-example-local" aria-controls="profile" data-toggle="tab">Local Events</a></li> + <li><a href="#events-example-remote" aria-controls="profile" data-toggle="tab">Remote Events</a></li> </ul> <!-- Tab panes --> @@ -104,6 +113,55 @@ under the License. rmtMsg.send("MyUnOrderedTopic", Integer.toString(i)); </pre> </div> + <div class="tab-pane" id="events-example-local"> + <pre class="brush:java"> + Ignite ignite = Ignition.ignite(); + + // Local listener that listenes to local events. + IgnitePredicate<CacheEvent> locLsnr = evt -> { + System.out.println("Received local event [evt=" + evt.name() + "]"); + + return true; // Continue listening. + }; + + // Subscribe to specified cache events occuring on local node. + ignite.events().localListen(locLsnr, + EventType.EVT_CACHE_OBJECT_PUT, + EventType.EVT_CACHE_OBJECT_REMOVED); + + // Get an instance of named cache. + final IgniteCache<Integer, String> cache = ignite.cache("cacheName"); + + // Generate cache events. + for (int i = 0; i < 20; i++) + cache.put(i, Integer.toString(i)); + </pre> + </div> + <div class="tab-pane" id="events-example-remote"> + <pre class="brush:java"> + Ignite ignite = Ignition.ignite(); + + // Get an instance of named cache. + final IgniteCache<Integer, String> cache = ignite.jcache("cacheName"); + + // Sample remote filter which only accepts events for keys + // that are greater than or equal to 10. + IgnitePredicate<CacheEvent> rmtLsnr = evt -> { + System.out.println("Received remote event [evt=" + evt.<Integer>key() >= 10 + "]"); + + return true; // Continue listening. + }; + + // Subscribe to specified cache events on all nodes that have cache running. + ignite.events(ignite.cluster().forCacheNodes("cacheName")).remoteListen(null, rmtLsnr, + EventType.EVT_CACHE_OBJECT_PUT, + EventType.EVT_CACHE_OBJECT_REMOVED); + + // Generate cache events. + for (int i = 0; i < 20; i++) + cache.put(i, Integer.toString(i)); + </pre> + </div> </div> </div> <div class="page-heading">GitHub Examples:</div> @@ -113,7 +171,7 @@ under the License. </p> </section> <section id="key-features" class="page-section"> - <h2>Messaging Features</h2> + <h2>Messaging & Events Features</h2> <table class="formatted" name="Messaging Features"> <thead> <tr> @@ -122,6 +180,28 @@ under the License. </tr> </thead> <tbody> + <tr> + <td class="left">Topic Based Messaging</td> + <td> + <p> + Ignite distributed messaging allows for topic based cluster-wide communication between all nodes. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/messaging"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Point-to-Point Messaging</td> + <td> + <p> + Ignite messages can be sent to either a group of nodes or to an individual node. + </p> + <div class="page-links"> + <a href="http://apacheignite.readme.io/docs/messaging"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> <tr> <td class="left">Ordered vs. Unordered</td> <td> @@ -135,18 +215,39 @@ under the License. </div> </td> </tr> - <tr> - <td class="left">Topic and Point-to-Point</td> - <td> - <p> - Ignite messaging works via topic based subscriptions. Topic messages can be sent - to either a group of nodes or to an individual node. - </p> - <div class="page-links"> - <a href="http://apacheignite.readme.io/docs/messaging"; target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> - </div> - </td> - </tr> + <tr> + <td class="left">Event Notifications</td> + <td> + <p> + Ignite distributed events functionality allows applications to receive notifications when a variety of events occur within the cluster. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/events"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Local vs. Remote Events</td> + <td> + <p> + Applications can get notified for task executions, read, write or query operations occurring on local or remote nodes within the cluster. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/events"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Automatic Batching</td> + <td> + <p> + Event notifications can be grouped together and sent in batches or timely intervals. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/automatic-batching"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> </tbody> </table> </section> Modified: ignite/site/trunk/features/streaming.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/streaming.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/features/streaming.html (original) +++ ignite/site/trunk/features/streaming.html Tue Mar 1 02:05:20 2016 @@ -238,6 +238,77 @@ under the License. </div> </td> </tr> + <tr> + <td class="left">JMS Data Streamer</td> + <td> + <p> + Ignite JMS Data Streamer consumes messages from JMS brokers and inserts them into Ignite caches. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/jms-data-streamer"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Apache Flume Sink</td> + <td> + <p> + IgniteSink is a Flume sink that extracts events from an associated Flume channel and injects into an Ignite cache. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/flume-data-streamer"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">MQTT Streamer</td> + <td> + <p> + Ignite MQTT Streamer consumes messages from a MQTT topic and feeds transformed key-value pairs into an Ignite cache. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/mqtt-streamer"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Twitter Streamer</td> + <td> + <p> + Ignite Twitter Streamer consumes messages from a Twitter Streaming API and inserts them into an Ignite cache. + </p> + </td> + </tr> + <tr> + <td class="left">Apache Kafka Streamer</td> + <td> + <p> + Ignite Kafka Data Streamer consumes messages for a given Kafka Topic from Kafka Broker and inserts them into an Ignite cache. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/kafka-streamer"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Apache Camel streamer</td> + <td> + <p> + Ignite Camel streamer consumes messages from an Apache Camel consumer endpoint and feeds them into an Ignite cache. + </p> + <div class="page-links"> + <a href="https://apacheignite.readme.io/docs/camel-streamer"; target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> + </div> + </td> + </tr> + <tr> + <td class="left">Apache Storm Streamer</td> + <td> + <p> + Ignite Storm Streamer consumes messages from an Apache Storm consumer endpoint and feeds them into an Ignite cache. + </p> + </td> + </tr> </tbody> </table> </section> Modified: ignite/site/trunk/includes/header.html URL: http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/includes/header.html (original) +++ ignite/site/trunk/includes/header.html Tue Mar 1 02:05:20 2016 @@ -26,7 +26,7 @@ <li><a href="/features/computegrid.html">Compute Grid</a></li> <li><a href="/features/streaming.html">Streaming & CEP</a></li> <li><a href="/features/datastructures.html">Data Structures</a></li> - <li><a href="/features/messaging.html">Messaging</a></li> + <li><a href="/features/messaging.html">Messaging & Events</a></li> <li><a href="/features/servicegrid.html">Service Grid</a></li> <li class="divider"></li> <li role="presentation" class="submenu-header">Hadoop & Spark</li> @@ -66,8 +66,8 @@ <li class="dropdown"> <a href="/addons.html">Add-ons<span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/addons.html#aiex" target="_blank">Apache Ignite Extensions</a></li> - <li><a href="/addons.html#web-console" target="_blank">GridGain Web Console</a></li> + <li><a href="/addons.html#aiex">Apache Ignite Extensions</a></li> + <li><a href="/addons.html#web-console">GridGain Web Console</a></li> </ul> </li> <li class="dropdown"> Modified: ignite/site/trunk/scss/ignite.scss URL: http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1732989&r1=1732988&r2=1732989&view=diff ============================================================================== --- ignite/site/trunk/scss/ignite.scss (original) +++ ignite/site/trunk/scss/ignite.scss Tue Mar 1 02:05:20 2016 @@ -548,9 +548,9 @@ section.usecase-page-section .first { } .page-menu { - margin-left : 35px; + text-indent: 20px; - padding: 20px 0 40px 0; + padding: 20px 0 0 0; & h3 { font-size: 21px !important; @@ -787,4 +787,39 @@ section#chatroom #gitter-badge { .addons-contibutor { font-size: 13px; -} \ No newline at end of file +} + +table.features { + & p { + margin-bottom: 20px !important; + } +} + +tr.sub-heading { + & > th { + background: #cfcfcf !important; + border: 1px solid #cfcfcf !important; + color: #000; + font-weight: bold; + } +} + +.feature-section { + padding: 90px 0 10px 0; + margin-top: -70px; +} + +.feature-header { + color: #333; + font-size: 24px; + + &:hover { + color: $red; + } +} + +.features-left { + padding-left: 20px !important; + font-weight: bold; + width :35%; +}
