mage titans usa 2016 - joshua warren - magento 2 integrations

@JoshuaSWarren #MageTitansUSA

About Me

• PHP-Based Ecommerce Developer Since 1999

• Magento Developer Since 2008; Magento 2 Developer Since 2014

• Magento Master

• Founder & CEO of Creatuity Corp, Magento Enterprise Solution Partner


Integrations


Discussing complex, data-intensive integrations


Let’s look at the new option in Magento 2


What is it? How do we use it?


Magento 1 Integration Options

• SOAP API

• REST API*


Magento 2 Integration Options

• SOAP API

• REST API

• Web Hooks*

• RabbitMQ*


RabbitMQ


Messaging Queue


Messages can be plaintext, process commands or any other type of

information.


Queue is a place where messages are held until a consumer connects and

retrieves them.


In other words…

RabbitMQ:These Go to 11

https://www.youtube.com/watch?v=KOO5S4vxi0o


RabbitMQ consistently sorts and delivers over one million messages per second

http://bit.ly/2c303Wy

http://bit.ly/2c303Wy


Magento hands a message off to RabbitMQ to be handled

asynchronously


RabbitMQ can be clustered as you scale up


RabbitMQ decouples your Magento code from your integrations using

messages


To harness the power of RabbitMQ…


think different


Bi-directional sync between an ERP/OMS and Magento

Old Way


When an order is placed, an event is fired and an observer handles sending

the order data to the ERP

New Way


Fire a message to RabbitMQ, move on


\Magento\Framework\MessageQueue\PublisherInterface $publisher

$publisher->publish('creatuity.sent.oms', $this->orderInterface);


Topics• ‘creatuity.sent.oms’ is the topic

• RabbitMQ can be configured to use topics to route messages to specific queues

• Wildcard routing is possible - i.e., ‘creatuity.*’ would match all topics that start with ‘creatuity.’

• Topics allow the consumers connected to RabbitMQ to easily grab only the messages they need to process

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/1.1/html/Messaging_User_Guide/chap-Messaging_User_Guide-Exchanges.html































































































































































































































Messages

• Can be an object, can be a string - can be anything you’d like

• Allows the application on either end of the integration to use their native format

• Keep it simple


Route responses to your Magento code via communication.xml


public function saveOmsNum(\Creatuity\Oms\Model\Oms $oms) { $oms->setData('MagentoOrderNum', $oms->getOrderNum()); $oms->setData('OmsOrderNum', $oms->getOmsNum()); $oms->save(); }


Advantages of RabbitMQ

• RabbitMQ can route messages to specific queues for you

• Decouples your code from the API on the other side of the integration

• There is a RabbitMQ client for every major language

• Magento developers write Magento code, ERP developers write ERP code


Gotchas

2.0

2.1 2.2


Magento 2.0, 2.1 and 2.2 all contain major changes to message queues


Magento Enterprise Edition Only


One more service to support in your web stack


Magento Cloud Edition is a good option to offset this


Homework


Go try RabbitMQ out


The key to success with RabbitMQ & all of Magento 2…


Stop trying to apply old patterns and techniques


Keep up with the new features and architectural advances


RabbitMQ enables us to quickly integrate third-party systems in a new way


We still don’t know the upper bound of Magento 2’s scalability


Go build something awesome!

mage titans usa 2016 - joshua warren - magento 2 integrations

Technology