Pros
Cons
A python framework for creating microservices
Microservices are classes with:
Wait...how does the client actually call the service?
A message broker implementing the Advanced Messaging Queue Protocol (AMQP), an open messaging protocol.
Don't run away, Nameko handles the RabbitMQ bits
Entrypoint: Exposes a method, often by monitoring an external entity (e.g. a queue)
Dependencies: "Gateways" to other code, not managed by the service (other services, databases, APIs)
Workers: Instance of a service class. Dependencies are replaced with result of `get_dependency`
Let's try it!
Let's try it!
Let's try it!
Let's try it!
"Great! How do I move all the things to microservices?"
Code available on GitHub
ripleyaffect/nameko_examples