This article describes serverless integration patterns based on choreography and orchestration, pro-cons, and when to use them — In a monolith, in-process communication between components happens either via method invocation of function calls. When you are building a cloud solution, communication between components is a lot harder. …

This article dives into serverless APIs, identifies key components and integrations to ensure best practices. — This is part of several writings about serverless. Previously wrote about what is serverless, design & technical trade offs, business benefits, market offerings comparison, service-full vs no-code, integration patterns: orchestration & choreography, voice apps and web apps. …

This article describes common multicloud architecture patterns, deployments and network topologies. It is the second part of the multicloud trends article published some weeks ago [1]. — A quick snapshot of the different patterns that this article will cover, which are split between distributed and redundant deployments [2].

The other day, I was talking to a Database Administrator about database fault tolerance and the different types of Transaction Logs. …

If new toys do not guarantee success, what does it? I go through my 6 key ingredients that will help with that. — Throwing new technologies like darts to a dartboard to see if we hit the solution. Dilbert’s comic strip seems incredible, but it happens. These are my 6 key ingredients to pay attention when changing the system/s architecture: New toys do not guarantee success Business/IT collaboration

This article describes the different programming languages and runtimes available in the major cloud vendors. What is the adoption and trends. — What programming languages are available in each cloud vendor? Cloud providers offer several runtime language options, so I wanted to understand which are the supported languages in each and built a table with a simple graph to compare.

This article describes a classic serverless scenario: the ubiquitous web application and identifies key components and integrations to ensure best practices. — This article is part of several writings about serverless. Previously wrote about what is serverless, design & technical trade offs, business benefits, market offerings comparison, service-full vs no-code, integration patterns: orchestration & choreography, and voice apps. …

This article describes a popular use case in serverless for voice applications and identifies key components and integrations to ensure best practices. — This article is part of several writings about serverless. Previously wrote about what is serverless, design & technical trade offs, business benefits, market offerings comparison, service-full vs no-code, integration patterns: orchestration & choreography. …

What is service-full serverless? And what are the differences with no-code solutions? — What is Service-full Serverless? Service-full serverless is about using and configuring managed services and features rather than writing, testing and releasing your own code. I would call it “integrating without glue code” for short. In practice, an example would be using API Gateway as a proxy to directly integrate with DynamoDB [1] without writing…