A Magento trainer and developer; announced three times a Magento Master; former Zend Z-Team member; speaker at many Magento conferences
Gerard has been a Software developer for almost 8 years, mainly doing Java backend work for web applications, a couple of times also using Kafka. In his spare time he also writes Rust and Clojure(script). He recently became interested in GraphQL and has made several related open source contributions.
Passionate about emerging technologies and likes to take technology to the extreme such as bridging Neuroscience with ML and GraphQL, Flying drones with React, and more. @googledevexpert ,author, speaker, #ReasonML,#web #React #ReactNative, #VueJS, #GraphQL,#VR, #AR
When the number of microservices in a specific site infrastructure grow, assuming that GraphQL is used througout that infrastructure, it might be that the new Magento 2.3 GraphQL also has a place in such an infrastructure and that schemas are stitched together using Apollo Federation. What parts of the Magento API would be useful and which other parts would better be replaced with alternative microservices? An honest look at the potential of Magento e-commerce in an Apollo Federation.
The common way to change data when using GraphQL is using mutations. These might be implemented by changing the database, and giving back the new state. But what if the backend uses CQRS, and writes might take a bit of time? In that case you could use subscriptions to handle changes.
Scaling GraphQL backend can be complicated process depending on your infrastructure. In this talk we will see how we can scale our GraphQL backend using Hasura engine, serverless functions and YugabyteDB. Typically even after scaling the backend we will be left with the problem of scaling our database. YugabyteDB will solve this problem for us by introducing fault tolerance and true global scaling of Distributed SQL.
Round Table. We will use a closed fishbowl conversation to run it. That means all the attendees will be in the same room. The host will pick a team of 5 people, who will be part of a fishbowl. This team will not be muted, being able to discuss the topic so that everyone else will be listening. All other people, except for the people in a fishbowl, will be muted. People who want to join the fishbowl should write in the chat that they want to join the conversation. Every 3 minutes one person in the fishbowl leaves (meaning he/she gets muted by the host) and the next one in the queue is unmuted. All this is done by the moderator (host).
Please be aware that the ticket only covers the cost of theevent, it does not include travel expenses.
Why do we charge a nominal fee?
We charge a nominal fee for community events in order to confirm attendance to ensure we have an accurate RSVP list. Our meetups are always over-subscribed so when people don't show it stops somone else attending.
What do we do with the fee?
By paying for the nominal fee you're supporting minorities in tech. You can read more about it in this link.
The payment confirmation email is your ticket.