iain_hecker

26 ms·

1.
by iain_hecker 12y ago
That's where SNS comes in. We publish to SNS which will fan out to multiple SQS queues. When a new service is built, it says to SNS "subscribe my queue to these topics". The publisher of the event doesn't know about the
2.
by iain_hecker 12y ago
We have all services running inside a VPN (see one of our older posts: https://blog.yourkarma.com/building-private-clouds-with-amaz... ) and we also use HTTP Basic token auth that are configured upon deployment. Every app ge
3.
by iain_hecker 12y ago
This. Also SOA means STD in Dutch, so we don't want to use it that often ;)
4.
by iain_hecker 12y ago
We use SQS for basically everything that happens asynchronously to the main flow. So when a user signs up there are a bunch of things that need to happen straight away (create an account, give 100MB to every new user), these go via HTTP. Th
5.
by iain_hecker 12y ago
Each app gets their own queue. So there is a queue for the shipment app and for the mailer app. When an event is published to SNS, it gets added to both queues.
6.
by iain_hecker 12y ago
Yup we are. There might be multiple applications interested in the event and they each get their own queue.
7.
by iain_hecker 12y ago
We will! There are however a couple of really nasty issues that we don't feel comfortable to release to the public yet.
8.
by iain_hecker 12y ago
It's easier to test individual items, for sure. Testing small code bases is the best thing ever. However, some actions require stuff to happen in multiple services. There are "contracts" on how to talk to other services. You