Downloaded 26 times
Uploaded byYaroslav Tkachenko
Why actor-based systems are the best for microservices
The document discusses the advantages of actor-based systems for microservices, emphasizing the importance of messaging for inter-service communication. It covers challenges faced with traditional HTTP APIs and highlights how the actor model simplifies distribution, concurrency, and message processing. Additionally, it presents various messaging patterns and emphasizes the performance and scalability benefits of using actors.
More Related Content
Similar to Why actor-based systems are the best for microservices
![Jms deep dive [con4864]](https://cdn.slidesharecdn.com/ss_thumbnails/jmsdeepdivecon4864-160927041349-thumbnail.jpg?width=640&height=640&fit=bounds)
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Why actor-based systems are the best for microservices
- 1. Why actor-based systemsare the best for microservices Yaroslav Tkachenko @sap1ens Director of Engineering, Platform at Bench Accounting
- 2.
- 3. Agenda • Microservices • Messagingfor microservices • EIP and messaging • Actors and messages • All combined… and more
- 4.
- 5.
- 6. Microservices Service A ServiceB HTTP API / RPC “Easy” way
- 7. Microservices Challenges with HTTPAPI / RPC: • Service discovery • Retries for failures • Routing and load balancing • Webhooks • Tracing • Versions • …
- 8.
- 9.
- 10. Messaging for microservices Weshould use only messaging for communication between microservices
- 11. Messaging for microservices ReactiveRevealed: Resiliency, Failures vs Errors, Isolation, Delegation and Replic
- 12. Messaging for microservices SurvivingMicro-services by Richard Rodger
- 13. Messaging for microservices SurvivingMicro-services by Richard Rodger
- 14.
- 15.
- 16. EIP and messaging EIPwas published in 2003 and it contains 65 patterns
- 17. EIP and messaging MessageChannel Message Pipes and Filters Message Router Message Translator Message Endpoint Point-to-Point Channel Publish-Subscribe Channel Datatype Channel Invalid Message Channel Dead Letter Channel Guaranteed Delivery Channel Adapter Messaging Bridge Message Bus Command Message Document Message Event Message Request-Reply Return Address Correlation Identifier Message Sequence Message Expiration Format Indicator Introduction to Message Routing Content-Based Router Message Filter Dynamic Router Recipient List Splitter Aggregator Resequencer Composed Message Processor Scatter-Gather Routing Slip Process Manager Message Broker Envelope Wrapper Content Enricher Content Filter Claim Check Normalizer Canonical Data Model Messaging Gateway Messaging Mapper Transactional Client Polling Consumer Event-Driven Consumer Competing Consumers Message Dispatcher Selective Consumer Durable Subscriber Idempotent Receiver Service Activator Control Bus Detour Wire Tap Message History Message Store Smart Proxy Test Message Channel Purger
- 18.
- 19. Actors and messages So,I convinced you that messaging patterns are great. Right?
- 20. Actors and messages Butwhy actors? I can just use a message queue and a bunch of consumers/producers
- 21. Actors and messages Sure!But let’s compare
- 22. Actors and messages ActiveMQmessage listener in Java
- 23. Actors and messages ActiveMQmessage listener in Java (zoom-in) public class Server implements MessageListener { // … public void onMessage(Message message) { try { TextMessage response = this.session.createTextMessage(); if (message instanceof TextMessage) { TextMessage txtMsg = (TextMessage) message; String messageText = txtMsg.getText(); response.setText(this.messageProtocol.handleProtocolMessage(messageText)); } response.setJMSCorrelationID(message.getJMSCorrelationID()); this.replyProducer.send(message.getJMSReplyTo(), response); } catch (JMSException e) { } } // … }
- 24. Actors and messages Actor-based(Akka) message listener in Scala class CustomerService extends Actor with ActorLogging with Consumer { val camel = CamelExtension(system) camel.context.addComponent("activemq", ActiveMQComponent.activeMQComponent( “tcp://localhost:61616” )) def endpointUri = "activemq:topic:events" def receive = { case e: CamelMessage => { sender() ! “SomeMessage” } } }
- 25. Actors and messages Btw,some magic is provided by: Apache Camel “The most unknown coolest library out there” JM
- 26. Actors and messages Actorsgive you: • Simple and high-level abstractions for distribution, concurrency and parallelism • Asynchronous, non-blocking and highly performant message-driven programming model • Very lightweight event-driven processes (several million actors per GB of heap memory)
- 27.
- 28.
- 29. All combined… andmore Summary: • It’s easy to build microservices from scratch using messaging patterns • All these patterns are well-known, tested and documented • Actor model gives very simple abstractions to process and send messages • Bonus: all kinds of routing models, back-pressure, reliable queues, broadcasts
- 30.
- 31.