REST APIs for Microservices? Beware!

REST APIs for Microservices? Beware!

CodeOpinion

54 года назад

49,613 Просмотров

Are you using REST APIs for a Microservices architecture? If you're using REST, HTTP APIs, gRPC, or any other Request/Response model as the primary way to communicate between microservices, you're going to need to deal with possibly hard to debug latency issues and address availability concerns.

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code & demos!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

🔥 Don't have the JOIN button? Support me on Patreon!
https://www.patreon.com/codeopinion

📝 Blog: https://codeopinion.com
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/

0:00 Intro
1:19 Distributed Transactions
2:36 Latency
5:42 Availability
6:26 Messaging
8:49 Resilience

#microservices #restapi #softwarearchitecture

Тэги:

#REST_APIs_for_Microservices #software_architecture #software_design #cqrs #design_patterns #software_architect #asp.net #soa #microservices #message_queues #kafka #event_bus #event_driven_architecture #azure_service_bus #rabbitmq #distributed_transactions #service_bus #mass_transit #message_queue #message_queuing #messaging_patterns #service_oriented_architecture #microservice_architecture #domain-driven_design #enterprise_service_bus #rest_api #rest_apis #http_api #Swagger
Ссылки и html тэги не поддерживаются


Комментарии: