addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Message-Based Architecture Using Amazon SQS for Your Internal APIs

Queues are great for buffering multiple systems so that they can scale independently. We keep our Web Service Tier light and fast by moving the slow and clunky operations to our queues using command pattern on top of message-based architecture.

These commands have become our internal API specification, and we have had great success with this pattern using the Amazon infrastructure. We would like to share these ideas with you over food and drink!

 

Our engineering blog is here: http://techblog.personalcapital.com/

</The Personal Capital Engineers>

Join or login to comment.

9 went

  • Ehsan L.
    VP of Engineering, Organizer,
    Event Host
  • A former member
    +1 guest
  • A former member
  • A former member
  • A former member
  • A former member

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy