A collection of 22 posts
About 3 years ago I learnt some basic Python, which I've used almost exclusively to build back-end APIs on AWS Serverless, mostly Lambda. This includes a monitoring solution on AWS, an event-driven API
About 3 years ago I learnt some basic Python, which I've used almost exclusively to build back-end APIs on AWS Serverless, mostly Lambda. This includes a monitoring solution on AWS, an event-driven API
How to integrate your AWS event-based system with external/legacy systems using RESTful APIs
Easy and practical example that shows when to use choreography and orchestration as modes of interaction in a microservices architecture, running on AWS Serverless
Telegram [https://telegram.org/] is a common messaging application, with over 500 million users. I've been using it daily since 2015, and I prefer it over WhatsApp due to many reasons: native PC/
tldr It shouldn’t be synchronous I’ve written about microservices [http://hacksaw.co.za/blog/architecture-predicts-devops-success/] before [http://hacksaw.co.za/blog/api-microservices-esb/], based on the work I did with the MAD-API