Search
Hiroaki Iwase
Lightning Talk: Ruby based Distributed Key Value Store 'ROMA'
Edit
Summarized using AI

Lightning Talk: Ruby based Distributed Key Value Store 'ROMA'

Hiroaki Iwase • June 04, 2015 • Singapore • Lightning Talk

In this lightning talk, Hiroaki Iwase presents ROMA (Ruby On-Memory Architecture), a distributed key-value store implemented in Ruby, aimed at enhancing data storage solutions. The talk is based on the growing significance of NoSQL databases and tackles the challenge of choosing the best solution for specific applications. Here are the key points discussed:

  • Introduction to ROMA: ROMA is described as a fully decentralized distributed system that employs a pure P2P architecture, similar to a distributed hash table, ensuring high availability and scalability.
  • Key Features of ROMA:
    • P2P Architecture: The system is designed using a peer-to-peer model which allows for scalability.
    • Data Replication and Recovery: ROMA replicates data and includes automatic recovery features, promoting high fault tolerance.
    • Modular Design: The architecture separates core logic from commands, allowing developers to easily introduce new functionalities.
    • Compatibility: ROMA supports a compatible protocol similar to Memcached, facilitating easy migration for users of similar databases.
    • Flexible Storage Options: Users can choose from various storage systems, including OS memory for caching purposes.
  • Introduction of Gladiator: Iwase highlights a GUI management tool named Gladiator, built for Ruby on Rails, which simplifies interactions with ROMA. Key functionalities of Gladiator include:
    • Connection management and analysis
    • Status setting
    • Log gathering Gladiator aims to make the management of ROMA more intuitive and user-friendly.
  • Usage Documentation: The speaker encourages developers to utilize resources available on GitHub for implementation methods such as Chef, DOA, and Ruby GS, and invites feedback and inquiries to foster community engagement.
  • Benchmarking ROMA against Competitors: Although refraining from naming specific competitors to avoid negative comparisons, Iwase shares that benchmarking results can be accessed on ROMA's homepage, comparing latency and throughput against other key-value stores.

In conclusion, ROMA represents an open-source solution for developers looking for a robust distributed key-value storage system, complemented by a user-friendly management tool, Gladiator. Iwase invites attendees and viewers to collaborate and engage with the development of ROMA, emphasizing its potential in the NoSQL domain.

Lightning Talk: Ruby based Distributed Key Value Store 'ROMA'
Hiroaki Iwase • June 04, 2015 • Singapore • Lightning Talk

Ruby based Distributed Key Value Store 'ROMA' by Hiroaki Iwase

I am going to introduce ROMA(Ruby/Rakuten On-Memory Architecture). ROMA is one of the data storing systems for distributed key-value stores. It is a completely decentralized distributed system that consists of multiple processes, called nodes, on several machines. It is based on pure P2P architecture like a distributed hash table, thus it provides high availability and scalability. This has been developed as an OSS product written in Ruby from 2007.

I will also share a GUI management tool named 'Gladiator', which is developed for Ruby on Rails, enabling developers to control ROMA more easily and intuitively.

Red Dot Ruby Conference 2015

00:00:19.560 uh thank you for giving me such a great
00:00:21.680 opportunity to attend our Tri so today I
00:00:24.880 want to introduce about
00:00:27.840 Roma uh I AI and now I'm working in the
00:00:31.480 L Inc and I use Ruby for the job L is a
00:00:35.840 Japanese isue company and we have a many
00:00:38.840 global Service in all over the
00:00:41.079 world in case of the southe Seria we
00:00:44.039 have tarat and biki and lo business and
00:00:47.520 specifically a Singapore Singapore
00:00:49.960 branch is a regional headquarter and we
00:00:52.840 develop the global Service from
00:00:54.840 Singapore so let's go to the main topic
00:00:58.359 so first topic is a Loma
00:01:01.079 so as you know the nosql is growing
00:01:03.559 rapidly and rapidly so nosql has many
00:01:06.040 good services like R reak and and
00:01:08.720 so on so but I think it is little
00:01:13.000 difficult to Choice the suitable product
00:01:15.439 for the your own
00:01:17.560 service so today I propose the best
00:01:21.360 solution solution is
00:01:25.479 uh
00:01:28.600 sorry so
00:01:30.600 isra Roma so of course I know that
00:01:34.320 everybody do not know the Roma so what
00:01:36.600 about
00:01:37.680 roma roma is a r Ruby on memory
00:01:40.600 architecture and it is a ruby based
00:01:43.000 disbility ke store and this is our
00:01:46.000 project homepage and SNS account so I
00:01:48.640 will show it again later please check
00:01:51.479 it Roma was a develop by ryt and RM and
00:01:56.039 R as OS
00:01:58.079 product and Roma has unique and good
00:02:00.840 speciality so first is R adapted pure
00:02:04.280 P2P architecture and using a consistent
00:02:07.320 hushing method so it means Roma have
00:02:10.520 high scaleability
00:02:12.319 and next is Roma replicated data and
00:02:15.640 recovering these data automatically when
00:02:17.599 er happening so it connected to the high
00:02:20.400 for
00:02:21.200 tolerance and next is a Roma Source
00:02:23.800 called are divided to the main logic and
00:02:26.200 each command and each function so uh the
00:02:30.519 so it means it enable to the developer
00:02:32.959 to add a new function and new command by
00:02:36.319 easily and also Roma have a MD
00:02:39.400 compatible protocol so if you are using
00:02:42.120 a micash now it is very easy to move the
00:02:45.440 Roma next is a storage system lar
00:02:48.879 adjusted to to the some storage system
00:02:52.200 so for example the Toyo cabinet and
00:02:55.120 gunga and SQ and of course you can use
00:02:58.680 OS memory like
00:03:00.920 cash so you can Choice the St type
00:03:03.840 depending on your
00:03:06.200 situation so next topic is a
00:03:09.239 gladiator gradior is a g Roma so what
00:03:13.599 can Gladiator do Gladiator can do
00:03:16.200 everything so for example
00:03:19.040 the not not kidding the cruster control
00:03:23.120 and Status setting and log Gathering and
00:03:27.680 connection analysis like a connection
00:03:29.319 card and connection resource rate and in
00:03:32.200 case of the just C management you have
00:03:34.120 to log in the server and check the
00:03:36.080 process and the connector tnet and check
00:03:38.640 the status so there has a many process
00:03:41.760 but in case of the using the Gladiator
00:03:43.720 so you can use the Roma more easily and
00:03:45.959 more
00:03:47.319 intuitively so final topic is how to use
00:03:50.120 a
00:03:50.760 Loma so this is our GitHub page so we
00:03:54.120 prepare the some method to use a Roma
00:03:56.040 for example chef and DOA and rby GS and
00:04:00.799 of course you can download the directory
00:04:02.400 via the
00:04:03.959 GitHub so and it is my request so if you
00:04:08.000 are using the Roma please send us the
00:04:09.920 your question and feedback and
00:04:12.560 request and then I want to pick up the
00:04:15.760 one frequently question so sometimes I
00:04:18.199 to inquiry about what difference between
00:04:20.799 the Loma and other KBS so but today I do
00:04:24.919 not pick up the specific product name
00:04:26.919 because of the I don't want to do the
00:04:28.560 negative campaign so I will just show
00:04:31.720 the bench mark result briefly so we did
00:04:35.240 a benchmark test with Roma and other KBS
00:04:38.800 and check their uh basic latency and
00:04:42.880 throughput so you can check the these
00:04:45.280 results from the our top page of the
00:04:47.240 latest article link is here so please
00:04:50.280 check it and as I said Roma is the open
00:04:54.560 source software so I sincerely hope that
00:04:57.680 you are joining the our project and send
00:04:59.720 the pro
00:05:00.880 request thank you
HI
Hiroaki Iwase
1 talk
Explore all talks recorded at Red Dot Ruby Conference 2015
+18