Databases
StackOverflow2013
Postsdbo
POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
    primarykey
    data
    text
    <p>I would like to build a fault-tolerant soft real-time web application for a pizza delivery shop. It should help the pizza shop to accept phone calls from customers, put them as orders into the system (via a CRM web client) and help the dispatchers to assign delivery drivers to the orders. </p> <p>These goals are nothing unusual, but I would like to make the service available 24/7, i.e. to make it fault-tolerant. Moreover, I would like to make it work very fast and to be very responsive. </p> <p>Below is a very simple architecture view for such an application.</p> <p><img src="https://i.stack.imgur.com/rZl2f.jpg" alt="pizza delivery shop orders system"></p> <p>The problem is that I do not know how to use all of the Erlang/OTP goodness to make the application very responsive and fault tolerant.</p> <p>Here are my questions:</p> <ol> <li>Which system elements should be replicated in order to provide fault-tolerance and how should I do that? I know that I can store the status of each vehicle (coordinates, assigned orders, etc.) in a replicated Mnesia database. Is that a right way to go? </li> <li>Which data-storage services should be conventional SQL-based (e.g. based on <a href="https://github.com/evanmiller/boss_db" rel="nofollow noreferrer">boss_db</a>) and which should be done on Mnesia to provide for very fast response? Is it ok to use a conventional SQL database to store customer records and history in a such fault-tolerant and highly-responsive application?</li> <li>Should I try to store all the data for all the services (customers, vehicles status, etc.) in RAM in order to make the application highly-responsive?</li> <li>Should I store the persistent vehicle data (id, capacity, etc.) in a conventional SQL database and store the real-time data (coordinates, assigned orders, orders in the trunk, etc.) in a Mnesia database to make the application more real-time responsive?</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USskanatek
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. USstemm
      1. VTFavorite
    2. VO
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. This table or related slice is empty.
      1. VTDownMod
    1. COIf you don't replicate all your application logic and data, how would you make the service 24/7 in case of e.g. a database server failure ;)
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. USTobias P.
    2. COCould you provide a reference on how to replicate data in a Erlang/OTP system which has 2+ nodes dealing with logic?
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. USskanatek
    3. COprocess group, send to all, conflict resolution or simply use riak/couchdb. Or you look at mnesia. But doing this by your own will be a really really hard task.
      singulars
      1. POBuilding a fault-tolerant soft real-time web application with Erlang/OTP
      1. USTobias P.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload