Why did you choose Mercure.rocks for your solution?


Can you introduce yourself and your project?


What are the results in the short term, the first metrics seen?


Could you tell us more about the next evolutions of your project?


Can you give us the technical context of your project?


Read a new case study made with our partner Brian McCluskey, director of engineering at <a href="https://ravencontrols.com" target="_blank" rel="noreferrer noopener nofollow">Raven Controls</a>. In this interview, he explains all the reasons why his team uses the <a href="https://mercure.rocks/" target="_blank" rel="noreferrer noopener">Mercure protocol</a>. 



<h2>Can you introduce yourself and your project?</h2>



Raven Controls are a start up delivering mission critical event and crisis management software. Our software has been deployed at some of the world’s biggest events, including UEFA Euro 2020 &amp; COP26 and we work with the biggest names in music, sports &amp; more, globally. 



One of the key capabilities of Raven is getting information into the right hands as quickly as possible so that decisions can be made quicker and incidents actioned and resolved faster.



<h2>Can you give us the technical context of your project?</h2>



Our web application and APIs are a Symfony application and we leverage React Native for our mobile app targeting iOS and Android. We’ve architected an event driven system and use SQS &amp; Symfony Messenger to process events. Realtime updates and notification are obviously a critical part of our system which is where Mercure comes in. We use Redis for our caching layer and as it was already part of our stack it made sense to use it as our transport for Mercure. 



Everything runs on AWS in Elastic Container Service and we have loads of awesome tooling like GitLab, Sentry and more.



<h2>Why did you choose Mercure.rocks for your solution?</h2>



We choose Mercure to provide the realtime capabilities in our system for several reasons. The fact that Mercure is batteries included. The protocol defines how Authentication, Automatic Reconnection, Pub/Sub etc should work and an implementation of the Hub brings these things working out of the box. With Websockets you have to create these things yourself or every vendor brings a different implementation which leads to vendor lock in.



Some of the unique features Mercure has like gathering missed events, and the subscription API, the open nature of it, and of course there are also integrations for Symfony. 



<h2>What are the results in the short term, the first metrics seen?</h2>



We adopted Mercure very early on in the project but compared to polling in an MVP we eliminated over 50% of our traffic. Our system is also designed to deal with what can be life threatening scenarios, the latency that polling would bring would cost time in critical situations and Mercure has helped us eliminate that. The ability to gather missed events has been a real win for us as stadia and arenas are often massive concrete structures built in areas with poor connectivity, this is great for users of our mobile app to instantly gather what happened when out of signal without having to poll our APIs constantly.



<h2>Could you tell us more about the next evolutions of your project?</h2>



We’re currently working on some Machine Learning projects. One predicts the key information relating to an incident and will display the results for selection in realtime, allowing a quicker time to creation of an incident, and also crucially, a quicker time to incident resolution as this will notify the right people of the incident faster. Another is surfacing threats by analysing information received from various sources. So plenty of use cases coming up where Mercure will be needed.







Thank you Brian for your time! Get more information about Raven Controls&#8217; projects with this talk given at <a href="https://api-platform.com/con/2022/conferences/real-time-and-beyond-with-mercure/" target="_blank" rel="noreferrer noopener">the API Platform Conference 2022</a>.

Raven Controls: using Mercure to keep high performance

Read a case study made with our partner Brian McCluskey, director of engineering at Raven Controls.

Raven Controls: using Mercure to keep high performance | Les-Tilleuls.coop

Accueil

Les-Tilleuls.coop

https://secure.gravatar.com/avatar/54fb8ea2a1a36c3b9ef44f25bf976b48?s=96&d=mm&r=g

Cécile Hamerel

&lt;?php

class LivingThing{}

class Animal extends LivingThing {}

class Cat extends Animal 
{
    public function __construct(
        public string $name,
        public bool $needToBeBrushed = true,
        public bool $needClawsCutting = true,
        public bool $needToBeFed = true
    ){}
}

interface AnimalShelter
{
    public function adopt(string $name): Animal;
}

class CatShelter implements AnimalShelter
{
    public function adopt(string $name): Cat
    {
        return new Cat($name);
    }
}

class BetterCatShelter implements AnimalShelter
{
    // The decorated instance is given
    public function __construct(private AnimalShelter $decorated)
    {}
     
    public function adopt(string $name): Cat
    {
        // We use the initial behavior of the decorated instance
        $cat = $this->decorated->adopt($name);
        
        // As well as an additional behavior
        $this->groom($cat);
        
        return $cat;
    }
     
    private function groom(Cat $cat)
    {
        $cat->needToBeBrushed = false;
        $cat->needClawsCutting = false;
        $cat->needToBeFed = false;
    }
}

class Me
{
    private Cat $cat;
     
    // Since the decorator has the same interface, 
    // I don't have to change anything in this class to use either
    public function getACatFromShelter(AnimalShelter $shelter, string $catName)
    {
        $this->cat = $shelter->adopt($catName);
    }
     
    public function checkCatStatus(): string
    {
        if (!$this->cat->needToBeBrushed &amp;&amp; !$this->cat->needClawsCutting &amp;&amp; !$this->cat->needToBeFed) {
            return "All is well for {$this->cat->name}.";
        }
        
        return "Wow... {$this->cat->name} needs attention!";
    }
}

$me = new Me();
$catShelter = new CatShelter();

$me->getACatFromShelter($catShelter, 'Cripper');
echo $me->checkCatStatus(). PHP_EOL;

$betterCatShelter = new BetterCatShelter($catShelter);
$me->getACatFromShelter($betterCatShelter, 'Jinjer');

echo $me->checkCatStatus(). PHP_EOL;

Applying the pattern with Symfony services


&lt;?php

// src/Mailer/LoggingMailer.php
namespace App\Mailer;

// ...
use Symfony\Component\DependencyInjection\Attribute\AsDecorator;

#[AsDecorator(decorates: Mailer::class)]
class LoggingMailer implements MailerInterface
{
<meta charset="utf-8"> // ...
}

&lt;?php

// ...

#[AsDecorator(
<meta charset="utf-8"> decorates: Mailer::class,
<meta charset="utf-8"> priority: 10,
<meta charset="utf-8"> onInvalid: ContainerInterface::IGNORE_ON_INVALID_REFERENCE,
)]
class LoggingMailer implements MailerInterface
{
<meta charset="utf-8"> // ...
}

&lt;?php
 
// ...
use Symfony\Component\DependencyInjection\Attribute\AsDecorator;
use Symfony\Component\DependencyInjection\Attribute\MapDecorated;

#[AsDecorator(decorates: Mailer::class)]
class LoggingMailer implements MailerInterface
{
    public function __construct(#[MapDecorated] &lt;meta charset="utf-8">MailerInterface $originalMailer)
    {
    	// ...
    }

    // ...
}

&lt;?php

class CrackersBox 
{
    private array $authorizedFlavours = ['bacon', 'cheese', 'onion cream', 'garlic and herbs'];
    protected array $crackers = [];
    
    public function getCracker()
    {
        if (empty($this->crackers)) {
            throw new RuntimeException('empty box!');
        }
        
        return array_shift($this->crackers);
    }
    
    public function insertCrackers(array $crackers) 
    {
        if (!empty($this->crackers)) {
            throw new RuntimeException('Finish what is left first!');
        }
        
        $this->crackers = array_filter($crackers, fn ($cracker) => in_array($cracker, $this->authorizedFlavours));
    }
}


$crackersBox = new CrackersBox();
$crackersBox->insertCrackers(['bacon', 'cheese', 'onion cream', 'garlic and herbs']);

echo $crackersBox->getCracker().PHP_EOL; // bacon
echo $crackersBox->getCracker().PHP_EOL; // cheese, no barbecue.

&lt;?php

class CrackersBox 
{
 protected array $authorizedFlavours = ['bacon', 'cheese', 'onion cream', 'garlic and herbs'];
 protected array $crackers = [];
 
 public function getCracker()
 {
 if (empty($this->crackers)) {
 throw new RuntimeException('empty box!');
 }
 
 return array_shift($this->crackers);
 }
 
 public function insertCrackers(array $<meta charset="utf-8">crackers) 
 {
 if (!empty($this->crackers)) {
 throw new RuntimeException('We finish the box first!');
 }
 
 $this->crackers = array_filter($crackers, fn ($cracker) => in_array($cracker, $this->authorizedFlavours));
 }
}

class CrackersBoxSortingCheese extends CrackersBox 
{
 public function getCracker()
 {
 while ('cheese' === $cracker = parent::getCracker()){
 $this->crackers[] = $cracker;
 }
 
 return $cracker;
 }
}


$crackersBox = new CrackersBoxSortingCheese();
$crackersBox->insertCrackers(['bacon', 'cheese', 'onion cream', 'garlic and herbs']);
echo $crackersBox->getCracker().PHP_EOL; // bacon
echo $crackersBox->getCracker().PHP_EOL; // onion cream... Phew, no cheese or barbecue

Description of the Liskov Substitution Principle


&lt;?php

interface LivingThingInterface {}
interface AnimalInterface extends LivingThingInterface {}

interface DogInterface extends AnimalInterface {}
interface PlantInterface extends LivingThingInterface {}


class Dog implements DogInterface {}

class Plant implements PlantInterface {}

class Pet
{
	public function __construct(AnimalInterface $animal) {}
}

class PetDog extends Pet
{
 	// Works
	public function __construct(DogInterface $dog)
	{
 		parent::__construct($dog);
	}
}

class PlantPet extends Pet
{
 	// Does not work
	public function __construct(PlantInterface $plant)
	{
 		parent::__construct($plant);
	}
}

&lt;?php

class LivingThing{}

class Plant extends LivingThing {}
class Animal extends LivingThing {}

class Cat extends Animal {}

interface AnimalShelter
{
	public function adopt(string $name): Animal;
}

class CatShelter implements AnimalShelter
{
 	// Works
	public function adopt(string $name): Cat
	{
 		return new Cat($name);
	}
}

class PlantShelter implements AnimalShelter
{
 	// Does not work
	public function adopt(string $name): Plant
	{
 		return new Plant($name);
	}
}

Pre-reading note: if you are unfamiliar with any of the terms, pause your reading and check their meaning before continuing!



In <a href="https://api-platform.com/" target="_blank" rel="noreferrer noopener">API Platform</a>, but also in <a href="https://les-tilleuls.coop/technologies/symfony" target="_blank" rel="noreferrer noopener">Symfony</a> &nbsp;— and in a lot of softwares &nbsp;— &nbsp;it is often recommended to &#8220;decorate&#8221; to extend third-party code. In API Platform, we are asked to decorate providers, processors, listeners, resolvers, factories…&nbsp; For an experienced dev, this is trivial. But if you are new to the term, it is not so obvious.



Before discussing the pattern, we need to understand the reasons for its existence. To do this, we must define the difference (in OOP) between composition and inheritance.



<h2>Inheritance</h2>



Inheritance is one of the four major concepts associated with object-oriented programming. It includes abstraction, encapsulation, inheritance and polymorphism. Inheritance allows us to acquire properties and methods from the base class in the derived (or child) class. Derived classes usually have a (logical) relationship with the base class.



<h3>Benefits of Inheritance</h3>



<ul>
<li>Inheritance allows code reuse, to easily inherit features from the parent class without copying the code.</li>



<li>It provides a clear hierarchical structure that allows us to break down a model into a simple, easily digestible structure.</li>
</ul>



<h3>Disadvantages of inheritance</h3>



<ul>
<li>Inherited functions are slower than normal functions (without mentioning any specific programming language).</li>



<li>All variables and methods of the base class are inherited even if they are not used, this causes an unnecessary surplus.</li>



<li>Small changes can affect all derived classes in unexpected ways due to tight coupling.</li>



<li>Inheritance has a structure defined at compile time: we cannot change anything in the higher classes when &#8220;distributing&#8221; public or protected methods and properties to derived classes. The details of the parent class are exposed to the child class and this breaks the fundamental concept of encapsulation (i.e. &#8220;hiding&#8221;, &#8220;keeping private&#8221; properties and methods, to control their contents and actions).</li>
</ul>



To make an analogy, if I put Crackers on the table for each person with 1 Cracker per person. Without supervision, after 2 or 3 greedy people, there is no more for the others. Then I put the Crackers in a dispenser (it would be a class) which is in charge of checking that only one is distributed to each person. No one can take one directly. I define an accessor `getCracker`. Once empty however, I can&#8217;t renew the stock. So I also define an `insertCrackers` mutator. Is it enough? No! I just allowed adding barbecue Cracker! Tragedy, they are not good! So my mutator will also be responsible for controlling the quality of the inserted Crackers.





We have properly protected the access and addition of Crackers!



If an implementation of a class is perfect from an encapsulation point of view, and if changes are applied on this class, no changes will be necessary in the classes that inherit from it. Only in reality, as soon as I extend the Crackers box, my new class will have knowledge of all the public and protected properties and methods.



Let&#8217;s just say I&#8217;m not in the mood for Cheese Crackers today and I want to sort out:





Let&#8217;s imagine that the brand that distributes these crackers decides to replace the cheese range with 3 variations: beaufort, comté and goat. When I update my `CrackersBox`, I will have to modify my `CrackersBoxSortingCheese`: the inheritance has broken the encapsulation contract.



<h2>Composition</h2>



In the composition, one of the classes has one or more instances of other classes often obtained by passing them to the constructor.



<h3>Advantages of the composition</h3>



<ul>
<li>Dependencies are less compared to inheritance, the idea being to rely mainly on typed arguments with the help of interfaces to be as versatile and resilient as possible in the future.</li>



<li>The objects are defined at runtime, they do not have the possibility to access the protected data of another object: this allows to maintain the encapsulation.</li>
</ul>



<h3>Disadvantages of the composition</h3>



<ul>
<li>It requires more time and produces more verbose code.</li>



<li>The system is dependent on the interrelation between the objects.</li>



<li>A good breakdown to keep flexibility while ensuring the scalability of the code without having to make a deep restructuring is difficult: it is necessary to spend some time upstream to study the possibilities of structures, design pattern, to make the optimal choice.</li>
</ul>



<h2>Why choose composition over inheritance</h2>



Composition is an object-oriented programming concept that stipulates that classes must have <a href="https://fr.wikipedia.org/wiki/Polymorphisme_(informatique)" target="_blank" rel="noreferrer noopener">polymorphic</a> behavior (we are talking about method overloading here, which is not possible in PHP for example). This makes the whole thing more flexible, easier to maintain despite a larger code at the beginning. This is the reason for the saying &#8220;<a href="https://en.wikipedia.org/wiki/Composition_over_inheritance" target="_blank" rel="noreferrer noopener">Favor object composition over class inheritance</a>&#8220;.



Inheritance is a powerful tool. If used well, it can make your code compact, easy to read and fast to develop, but there are many pitfalls a person can easily fall into. Small changes can have disastrous consequences as seen above. That&#8217;s why, as a rule, we opt for composition instead.



<h2>When to inherit or not?</h2>



Let&#8217;s look at some OOP typing rules and the limits they impose. With these in mind, you will be able to identify situations where inheriting is not a good solution.



Do you know Barbara Liskov? She produced a publication called &#8220;A behavioral notion of subtyping&#8221; where she formalized the Liskov Substitution Principle, one of the <a href="https://fr.wikipedia.org/wiki/SOLID_(informatique)" target="_blank" rel="noreferrer noopener">SOLID</a> principles. I encourage you to study these principles (and <a href="https://fr.wikipedia.org/wiki/Loi_de_D%C3%A9m%C3%A9ter" target="_blank" rel="noreferrer noopener">Demeter&#8217;s Law</a>).



<h3>Description of the Liskov Substitution Principle</h3>



If S is a subtype of T, then objects of type T in a program can be replaced by objects of type S without altering any properties of that program.



Liskov&#8217;s substitution principle imposes certain requirements on method signatures in OOP languages. Among them, two notions that we will detail:



<ul>
<li>Respecting the contravariance of method parameter types in the subtype.</li>



<li>Respecting the covariance of the return types of the methods in the subtype.</li>
</ul>



<h3>Covariance and Contravariance</h3>



Many programming languages support subtyping. For example, if the type Cat is a subtype of Animal, an element of type Cat should be accepted wherever an element of type Animal is used.



Variance refers to how subtyping between more complex types relates to subtyping between their components. For example, how should a list of cats identify itself as a list of animals? Or how should a function that returns a cat identify as a function that returns an animal? These sentences are complex, and nothing beats a hands-on example to get the hang of the rule.



<h4>Example of contravariance in PHP</h4>





DogInterface inherits from AnimalInterface, the inheritance tolerates this change of type, it is the contravariance. S subtype of T -&gt; S being DogInterface and T being AnimalInterface.



PlantInterface inherits from LivingThingInterface, just like Animal. However PlantInterface is not a subtype of AnimalInterface, it is a subtype of LivingThingInterface.



Let&#8217;s consider it as a cousin. Inheritance will refuse this type change.



An example of covariance in PHP





Cat inherits from Animal, the inheritance tolerates this change of type, it is the contravariance. S subtype of T -&gt; S being Cat and T being Animal.



Plant inherits from LivingThingInterface, just like Animal. However Plant is not a subtype of Animal. It is a subtype of LivingThing.



Consider it a cousin. Inheritance will refuse this change of type.



Note that by the obviousness of the names used, it seems strange to have classified Plant under Animal, but it is not always so obvious. A better structure would have been to have everything derived from LivingThing.



Also, new exceptions should not be thrown by methods of the subtype, unless they are subtypes of exceptions thrown by methods of the supertype. You are beginning to see the limits of inheritance!



There comes a point in our structures where these relationships conflict with what we want to accomplish. So, rather than inheriting to add behavior, it becomes clearer by creating classes that do just what is desired and injecting them into classes that need that behavior. As a bonus, these classes can be used more easily.



Composition makes a lot more sense, all right. And what about the decoration?



The pattern



Let&#8217;s say we have used composition in our code. Among the SOLID principles is also the O for Open/Closed Principle. This principle states: that software entities (classes, modules, functions, etc.) should be open to extension, but closed to modification. That is, such an entity can allow its behavior to be extended without changing its source code.



How to add behavior to a class, but without touching its interface and signatures, without adding new methods? It is possible to inherit and overload, but we don&#8217;t want to fall back into the limitations we saw above. So we compose. We compose by decorating!



A decorator is a class. It is a class that exposes the same interface(s) as the class it is decorating, that it wants to extend. This is not enough of course, to complete the decoration, it will be necessary to pass an instance of the decorated class to the class which decorates it, often via its constructor. The most common image to visualize this operation is that of Russian dolls nesting in each other. This is also known as onion architecture.



An example with PHP





Don&#8217;t hesitate to play with this example, to mess with it to understand the mechanics. For example, have fun adding a CollarOptionCatShelter that puts a collar on the cat when you pay more.



And try to decorate CatShelter, and/or BetterCatShelter.



<h3>Applying the pattern with Symfony services</h3>



In Symfony, all classes registered as services are decoratable. In version 6.1 of the framework, here is how to do it (taken from the documentation: <a href="https://symfony.com/blog/new-in-symfony-6-1-service-decoration-attributes" target="_blank" rel="noreferrer noopener">https://symfony.com/blog/new-in-symfony-6-1-service-decoration-attributes</a>). You can also refer to our cooperator Robin&#8217;s talk: <a href="https://slides.com/chalasr/symfonybc-promise-demystifed/" target="_blank" rel="noreferrer noopener">https://slides.com/chalasr/symfonybc-promise-demystifed/</a>.



Consider the common case where you want to decorate a service (e.g. Mailer) with a new service that adds logging capabilities to it (e.g. LoggingMailer). Here&#8217;s how you can set up the decoration with PHP attributes: Both classes should implement a common interface. Here MailerInterface.





The <code>#[AsDecorator]</code> attribute supports any additional options you may need:





If you need to access the decorated service from within the decorator service, add the <code>#[MapDecorated]</code> attribute to one of the service constructor arguments:





<blockquote class="wp-block-quote">
Be careful not to decorate a service that is used as an Alias in Symfony, to avoid looking for reasons why the code doesn&#8217;t work. Symfony&#8217;s dependency injection does not yet support Alias decoration.




<cite>From Baptiste, Antoine, Vincent, Robin, Myself&#8230; (and all those who have suffered from it)</cite></blockquote>



I hope this concept is a bit clearer for you now. For your personal monitoring, don&#8217;t hesitate to <a href="https://symfony.com/doc/current/service_container/service_decoration.html" target="_blank" rel="noreferrer noopener">check this Symfony</a> post on the different ways to decorate a service. 



Enjoy your code!

Mastering the decorator pattern

Dive into a tutorial about the decorator pattern and its specificities with our cooperator Grégoire Hébert.

Mastering the decorator pattern | Les-Tilleuls.coop

https://secure.gravatar.com/avatar/b473bd9d058c922e08d57f39a4a861db?s=96&d=mm&r=g

Grégoire Hébert

The second edition of <a href="https://api-platform.com/con/2022/" target="_blank" rel="noreferrer noopener">API Platform Conference</a> is around the corner! Join us on Thursday 15 and Friday 16 September in Lille and online. Two stages are scheduled in French and in English. Both of them will be broadcasted live on Livestorm. 



<h2>An intensive week of knowledge sharing </h2>



Let&#8217;s see together <a href="https://api-platform.com/con/2022/" target="_blank" rel="noreferrer noopener">a sneak peek of the conference schedule!</a> 



<ul><li><a href="https://api-platform.com/con/2022/conferences/php-websockets-or-how-to-communicate-with-clients-in-real-time/" target="_blank" rel="noreferrer noopener">Pauline Vos</a> will speak about&nbsp;PHP Websockets</li><li><a href="https://api-platform.com/con/2022/conferences/dilemmas-and-decisions-what-we-ve-learned-designing-the-new-sylius-api/" target="_blank" rel="noreferrer noopener">Lukasz Chrusciel</a> will share news from Sylius&#8217; new API</li><li><a href="https://api-platform.com/con/2022/conferences/domain-driven-design-with-api-platform-3/" target="_blank" rel="noreferrer noopener">Robin Chalas and Mathias Arlaud</a> will speak about DDD with API Platform 3</li><li><a href="https://api-platform.com/con/2022/conferences/gerer-les-operations-sequentielles-avec-REST/" target="_blank" rel="noreferrer noopener">Grégoire Hébert</a> will show you how to manage sequential operations with REST&nbsp;</li><li><a href="https://api-platform.com/con/2022/conferences/building-schema-first-event-driven-architectures-with-async-api/" target="_blank" rel="noreferrer noopener">Fran Mendez</a> will present schema-first event-driven architectures with AsyncAPI</li><li><a href="https://api-platform.com/con/2022/conferences/API-platform-au-quotidien-dans-une-entreprise-e-commerce-et-logistique/" target="_blank" rel="noreferrer noopener">Kévin Verschaeve and Clément Sanchez</a> will show how API Platform works in the daily life of an e-commerce and logistics company</li><li><a href="https://api-platform.com/con/2022/conferences/decentralizaion-query-apis-and-other-myths/" target="_blank" rel="noreferrer noopener">Ruben Verborgh</a> will speak about decentralization, query APIs and other myths</li><li><a href="https://api-platform.com/con/2022/conferences/la-revue-de-code-est-un-art/" target="_blank" rel="noreferrer noopener">Smaïne Millianni</a> will present a talk about code review</li><li><a href="https://api-platform.com/con/2022/conferences/fighting-impostor-syndrome-a-pratical-handbook/" target="_blank" rel="noreferrer noopener">Marine Gandy</a> will talk about impostor syndrome</li><li><a href="https://api-platform.com/con/2022/conferences/what-s-new-in-caddy-the-webserver-of-api-platform/" target="_blank" rel="noreferrer noopener">Francis Lavoie</a> will show you what&#8217;s new in Caddy, API Platform&#8217;s webserver</li><li><a href="https://api-platform.com/con/2022/conferences/webauthn-se-debarrasser-des-mots-de-passe-definitivement/">Florent Morselli</a> will share thoughts about&nbsp;Webauthn</li></ul>



More speakers are announced on <a href="https://api-platform.com/con/2022/schedule" target="_blank" rel="noreferrer noopener">our website</a>!



Interested in getting trained about API Platform? <a href="https://api-platform.com/con/2022/schedule" target="_blank" rel="noreferrer noopener">Two workshops are also available</a>:



<ul><li>Tuesday 13/09: <a href="https://api-platform.com/con/2022/conferences/designing-and-building-an-api-first-project-with-API-Platform-3/" target="_blank" rel="noreferrer noopener">Design and development of a 1st API project with API Platform 3,</a> with <a href="https://twitter.com/dunglas" target="_blank" rel="noreferrer noopener">Kévin Dunglas</a> and <a href="https://twitter.com/s0yuka" target="_blank" rel="noreferrer noopener">Antoine Bluchet</a></li><li>Wednesday 14/09: <a href="https://api-platform.com/con/2022/conferences/workshop-domain-driven-design-with-API-Platform-3/" target="_blank" rel="noreferrer noopener">Domain Driven Design with API Platform 3</a>, with <a href="https://twitter.com/chalas_r" target="_blank" rel="noreferrer noopener">Robin Chalas</a> and <a href="https://twitter.com/matarld" target="_blank" rel="noreferrer noopener">Mathias Arlaud</a></li></ul>



When you register to the on-site conference, you can also join our <a href="https://api-platform.com/con/2022/conferences/API-platform-3-hack-day/" target="_blank" rel="noreferrer noopener">hackday</a> planned on Saturday 17/09. It&#8217;s free and it will be hosted by Kévin Dunglas and Antoine Bluchet in our office.



Moreover, we also remind you that all tickets are free for student or job seekers. <a href="mailto:events@les-tilleuls.coop" target="_blank" rel="noreferrer noopener">Contact our team</a> to get your voucher.



<h2>Thanks to our partners</h2>



This event would not have been possible without our partners support! Many thanks to <a href="https://www.francetelevisions.fr/" target="_blank" rel="noreferrer noopener nofollow">France Télévisions</a>, <a href="https://sensiolabs.com/fr/" target="_blank" rel="noreferrer noopener nofollow">Sensiolabs</a>, <a href="https://www.alicesgarden.fr/" target="_blank" rel="noreferrer noopener nofollow">Alice&#8217;s Garden</a>, <a href="https://link-value.fr/" target="_blank" rel="noreferrer noopener nofollow">Linkvalue</a>, <a href="https://platform.sh/" target="_blank" rel="noreferrer noopener nofollow">Platform.sh</a>, <a href="https://www.apimatic.io/" target="_blank" rel="noreferrer noopener nofollow">APImatic</a> and <a href="https://fairness.coop/" target="_blank" rel="noreferrer noopener nofollow">Fairness</a> for contributing to the organization of this event! Want to be a partner? Some slots are still available: <a href="mailto:events@les-tilleuls.coop" target="_blank" rel="noreferrer noopener">contact us to get the sponsorship brochure</a>. 







We are really excited to meet you both online and in Lille for <a href="https://les-tilleuls.coop/en/blog/api-platform-conference-2021-a-successful-edition" target="_blank" rel="noreferrer noopener">this second edition</a>! Still not registered? <a href="https://api-platform.com/con/2021/#pricing" target="_blank" rel="noreferrer noopener">Late bird tickets are still available.</a> See you soon!

API Platform Conference 2022: join us and meet the best API experts!

Only one month left until API Platform Conference 2022. Join us and let's see together a sneak peek of the entire schedule!

Join API Platform Conference

A few weeks ago, <a href="https://les-tilleuls.coop/fr/blog/click-and-collect-sylius" target="_blank" rel="noreferrer noopener">we announced the release of Sylius Click &#8216;N&#8217; Collect</a>, a solution to sell and hand over products safely during the lockdown (and even after that). Creating an e-commerce store, setting up all its parameters or managing its own servers can be complex and quickly time-consuming tasks.



We are now pleased to announce the availability of a hosted version of Sylius Click &#8216;N&#8217; Collect! On <a href="http://click-n-collect.shop" target="_blank" rel="noopener">click-n-collect.shop</a>, you can get a ready-to-use shop in a few minutes. <a href="http://click-n-collect.shop" target="_blank" rel="noopener">Find out here how to create your shop</a> and start selling now!



<figure class="wp-block-image"><a href="https://www.click-n-collect.shop/en" target="_blank" rel="noopener"><img decoding="async" src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/343.jpg" alt="logosponsor" title="logosponsor"/></a></figure>







Our hosted version comes with :



<ul><li style="text-align: justify;">An optimal default configuration allowing you to sell immediately (languages, in-store payment, categories, taxonomy, Click &#8216;N&#8217; collect&#8230;)</li><li style="text-align: justify;">Online payment, by credit card thanks to Paypal or Stripe, as well as in store (other payment solutions can be added on request)</li><li style="text-align: justify;">The ability to ship orders, or of course, to offer in-store pick-up or drive-through via our Click and Collect module</li><li style="text-align: justify;">Inventory management</li><li style="text-align: justify;">Issuing invoices</li><li style="text-align: justify;">Refundings</li><li style="text-align: justify;">Help on the setting up of your shop</li><li style="text-align: justify;">Customization features (logo, general terms and conditions of sales, footer, order confirmation e-mails, etc.)&nbsp;</li><li style="text-align: justify;">Multiple stores/channels sellings</li><li style="text-align: justify;">Support for multiple languages and currencies (e.g. English + French, Pounds + Euros)</li><li style="text-align: justify;">High availability hosting based on Kubernetes The ability to use a custom domain name</li><li style="text-align: justify;">The 100% automatic implementation of HTTPS for a safer experience</li></ul>



Continue your activity during lockdown by creating your <a rel="noopener" href="https://www.click-n-collect.shop/en" target="_blank">Click and Collect store in a few clicks</a>! The hosted version of Sylius Click &#8216;N&#8217; Collect is free of charge for worker cooperatives and organizations with less than 10 employees. Need more information? <a href="https://les-tilleuls.coop/en/" target="_blank" rel="noreferrer noopener">Contact us</a>, we remain available remotely.

Sylius Click ‘N’ Collect is now available as a hosted version!

A few weeks ago, we announced the release of Sylius Click &#8216;N&#8217; Collect, a solution to sell and hand over products safely during the lockdown (and even after that). Creating an e-commerce store, setting up all its parameters or managing its own servers can be complex and quickly time-consuming tasks. We are now pleased to [&hellip;]

Sylius Click ‘N’ Collect is now available as a hosted version! | Les-Tilleuls.coop

Because of the coronavirus pandemic, a large part of the world is under lockdown and most shops are closed or with long queues.



<a href="https://click-n-collect.shop/en" target="_blank" rel="noopener">Sylius Click &#8216;N&#8217; Collect </a>is a solution to sell and hand over your products safely during the lockdown (and even after that). By allowing contactless pick up and preventing queues, Sylius Click &#8216;N&#8217; Collect protects your workers and your customers.



Sylius Click &#8216;N&#8217; Collect is a plugin for the <a href="https://sylius.com/" target="_blank" rel="noopener">Sylius eCommerce platform</a>. It&#8217;s free (as in speech, and as in beer), and it&#8217;s brought to you by our little hands. It can also be used in addition to all the existing features and plugins of Sylius.



<figure class="wp-block-image"><a href="https://click-n-collect.shop/en" target="_blank" rel="noopener"><img decoding="async" src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/343.jpg" alt="logosponsor" title="logosponsor"/></a></figure>







<h3>How does it work?</h3>



<iframe loading="lazy" src="https://www.youtube.com/embed/bQ9_vQJf-2I" allowfullscreen="allowfullscreen" width="560" height="315" frameborder="0"></iframe>



As a customer:



<ol><li>Go on the shop&#8217;s website</li><li>Select the products to order</li><li>Select the collect location (e.g. the physical shop)</li><li>Select an available time slot</li><li>Pay online, or select in-store payment (Stripe and PayPal are also supported).</li><li>Optional: a PIN is generated, you&#8217;ll need it to retrieve the order</li><li>Pick up your order at the shop during the selected time slot! Use the PIN code to unlock the box if appropriate.</li></ol>



<figure class="wp-block-image"><a href="https://click-n-collect.shop/en" target="_blank" rel="noreferrer noopener"><img decoding="async" src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/341.png" alt="en client" title="EN Client"/></a></figure>



As a seller:



<ol><li>Use the timetable in the admin interface to see the upcoming orders</li><li>Prepare the orders: put them in a bag and make the order number noticeable (staple it or use a marker)</li><li>Clean carefully the shelf and the lock (if appropriate) with the appropriate cleaning products</li><li>Put the bag in the shelf</li><li>Optional: use the PIN to lock the box in the shelf to secure the order</li><li>Monitor the pick up from afar, from behind a window, or using CCTV</li></ol>



<figure class="wp-block-image"><a href="https://click-n-collect.shop/en" target="_blank" rel="noreferrer noopener"><img decoding="async" src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/340.png" alt="enn" title="en"/></a></figure>



Repeat! You&#8217;re now selling while preventing the pandemic to spread!



<h3>How to install?</h3>



Our guidelines are at your disposal&nbsp;<a href="https://github.com/coopTilleuls/CoopTilleulsSyliusClickNCollectPlugin" target="_blank" rel="noreferrer noopener">on Github</a>&nbsp;and a demo can be tried at this adress: <a href="https://demo.click-n-collect.shop/en_US/">https://demo.click-n-collect.shop/en_US/</a>.&nbsp;Sylius Click &#8216;N&#8217; Collect is licensed under&nbsp;<a href="https://github.com/coopTilleuls/CoopTilleulsSyliusClickNCollectPlugin/blob/master/LICENSE">AGPL-3.0</a>. For companies not wanting, or not able to use AGPL-3.0 licensed software, commercial licenses are also available.&nbsp;<a href="mailto:gregory@les-tilleuls.coop">Contact us for more information, we remain avaiilable at a distance!</a>

Sylius Click 'N' Collect: sell and hand over securely during the coronavirus pandemic!

Because of the coronavirus pandemic, a large part of the world is under lockdown and most shops are closed or with long queues. Sylius Click &#8216;N&#8217; Collect is a solution to sell and hand over your products safely during the lockdown (and even after that). By allowing contactless pick up and preventing queues, Sylius Click [&hellip;]

What's new at Les-Tilleuls.coop ?

Raven Controls: using Mercure to keep high performance

Mastering the decorator pattern

API Platform Conference 2022: join us and meet the best API experts!

Sylius Click ‘N’ Collect is now available as a hosted version!

Sylius Click 'N' Collect: sell and hand over securely during the coronavirus pandemic!