As you probably already noticed, the cloud is a hot and recurrent topic in today’s conversations.
We repeatedly hear buzz words like AWS Lambdas, Kubernetes, Azure functions, and much more. It’s incredible and sometimes stressful, to see and realize the enormous number of functionalities these companies supply to their clients.
As software engineers, it’s a requirement to get everything up to speed and keep up with the market speed and innovation, so we don’t lose the train.
In today’s article, I will mainly focus on the Azure functions:
Successful people are simply those with successful habits — Brian Trancy
We all know that our working routines, as well as our productivity, suffered a significant change after we got into this pandemic stage.
Probably most people increased the spending time on Netflix, video games, social media, etc. I admit… I was one of them!
Fortunately, as a software engineer, our sector didn’t get affected much by the plague. Most of us just needed to switch our laptop’s location, and that was it, we were ready to start over again.
I knew I wanted more. I didn’t want to spend…
When was the last time you needed to submit or extract some data from a website, and it took an eternity?
Caching is a well-known concept, and it has existed for a very long time.
Unfortunately, many applications fail to extract their full potential. With such a system within your application, your response times can become significantly faster, without much work.
Your clients will thank you later!
Today, I will explain to you, what and how through the following topics:
In a microservice architecture, sometimes we want to ensure behaviors across all services, such as: request tracking, logging, header validation, and so on.
To consistently enforce such policies, we shouldn’t throw those responsibilities to all teams responsible for each group of microservices, or each one would develop their solution, and the word “consistency” would boil away.
Focusing the logic above in what’s called Policy Enforcement Point (PEP) is the best decision you can make. …
The capacity to learn is a gift; the ability to learn is a skill; the willingness to learn is a choice. — Brian Herbert
Most rookies, whenever they hear the word API in a conversation or an article, some interesting thoughts may come to their minds, like complexity, unknown, difficulty, etc.
There’s no problem with that, we all must start from somewhere right? …
We all want our applications to be secure, bug-free, and resilient to any type of problems right? This article is all about client resiliency and how to achieve it.
Most software engineers and architects look to apply patterns, mostly related to infrastructure or service failure, and the normal solution we look for is redundancy, wherewith load balancing, for example infrastructure segregation, we try to avoid the big word, failure.
In this article, I will explain to you the main concept of “Circuit Breaker” and how it will help you bulletproof your microservices, and make them resilient to external problems with…
Be the change you wish to see in the world. — Mahatma Gandhi
The search for physical addresses around services within our microservices is a well-known concept since the beginning of distributed computing. It’s a key piece of our architecture since it directly affects our distributed architecture, starting with the following three key reasons:
Inevitably when your application configuration is written directly into the code, every time you need to apply a change, the application must be recompiled or/and redeployed, for the client’s well-being or even for the folk that does that work, avoid it. Most engineers separate the configuration information from the original application source due to the lack of efficiency and flexibility.
Five usual solutions to this problem take place. In this article, I propose one of those solutions, mainly the most straightforward, Spring Cloud Configuration Server.
Looking at the official Spring.io documentation:
Spring Cloud Config provides server-side and client-side support for…
“I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do It“. — Bill Gates
This quote is quite what we, as developers are always looking for — an easy way to achieve what we want — and nothing better than shortcuts with the same outcome.
With these 4 tips, you will find yourself more available to think about the real problem instead of getting stuck on the usual “how to get there” problem.
For those who don’t know what live templates are about, it’s mostly about what autocomplete recommendations…
As a software engineer, creating good and reliable solutions is my everyday goal. Within my articles, I try to express all the excitement and passion around it!