Baratine vs Geode?
152 views
Skip to first unread message
Rick Mann
May 18, 2015, 2:00:06 PM5/18/15
to barat...@googlegroups.com
How does Caucho's Baratine compare to Apache Geode?
Scott Ferguson
May 18, 2015, 6:12:11 PM5/18/15
to barat...@googlegroups.com
On 5/18/15 11:00 AM, Rick Mann wrote:
How does Caucho's Baratine compare to Apache Geode?
Different focus, from what I've read about Geode.
Geode starts from a distributed cache/database and extends features from there.
Baratine starts from a service platform (microservices, SOA) and extends.
For Baratine we're working on a long example based on Lucene, treating Lucene as a service.
A progression for Lucene as a Baratine service might look like:
1. Publish Lucene as a REST/jamp/websocket service, i.e. single-server Solr, using Baratine. The developer creates a simple facade to expose Lucene's API to an external REST/websocket API. In a way, using Baratine as a JAX-RS replacement with websockets/async as a bonus.
2. Turn Lucene/Baratine into a distributed service with sharding/partitioning and Baratine's map/reduce (Solr cloud.)
3. Use Baratine's distributed store/database instead of Lucene's native, enabling failover and improving performance.
An existing application service might go through the same process. Lucene's a nice example because it's a fairly large service.
Or for a new service, you could start with #3.
Geode starts with its distributed store/database and builds a service from that. Its core model is the database, where Baratine's core model is the service.
-- Scott
Geode starts from a distributed cache/database and extends features from there.
Baratine starts from a service platform (microservices, SOA) and extends.
For Baratine we're working on a long example based on Lucene, treating Lucene as a service.
A progression for Lucene as a Baratine service might look like:
1. Publish Lucene as a REST/jamp/websocket service, i.e. single-server Solr, using Baratine. The developer creates a simple facade to expose Lucene's API to an external REST/websocket API. In a way, using Baratine as a JAX-RS replacement with websockets/async as a bonus.
2. Turn Lucene/Baratine into a distributed service with sharding/partitioning and Baratine's map/reduce (Solr cloud.)
3. Use Baratine's distributed store/database instead of Lucene's native, enabling failover and improving performance.
An existing application service might go through the same process. Lucene's a nice example because it's a fairly large service.
Or for a new service, you could start with #3.
Geode starts with its distributed store/database and builds a service from that. Its core model is the database, where Baratine's core model is the service.
-- Scott
--
You received this message because you are subscribed to the Google Groups "Baratine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to baratine-io...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages