Wow. Very nice, well done. Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ?
> On 25 Sep 2018, at 12:20, Norbert Hartl <norb...@hartl.name> wrote: > > As presented on ESUG here is the brief description of one of our current > projects. > > Mobility Map > —————— > > Mobility Map is a broker for mobility services. It offers multi-modal routing > search enabling users to find the best travel options between locations. > Travel options include car sharing, bikes, trains, busses etc. Rented cars > can be offered for ride sharing on booking time letting other people find it > to participate in the ride. Single travel options are combined in travel > plans that can be booked and managed in a very easy way. > > For this project main requirements were scalability to serve a large user > base and flexibility to add more additional providers to the broker. The > application has been realized using web technologies for the frontend and > pharo for the backend. Using a microservice architecture combined with a > broker it is easy to extend the platform with additional brokers. Deployment > is done using docker swarm for distributing dozens of pharo images among > multiple server machines connected by a message queue for the communication. > Pharo supported that scenario very well enabling us the meet the requirements > with less effort. > > Pharo turned out to be a perfect fit to develop the application in a agile > way. Small development cycles with continuous integration and continuous > delivery enables fast turnarounds for the customers to validate progress. > > This is a screenshot of the search page for multi-modal results: > > > <Screen Shot 2018-09-21 at 16.54.30.png>
