In this article I show how I use the OpenAPI specs in microservices polyglot design.
Often microservices architectures are composed by a bunch of modules use the same interface playing different roles :sometime as client or server, sometime as client and server at the same time. In add each module can be developed in different language and technology and moreover the same interface can be used by test and load tools. …
The art of recycling old pieces of hardware giving it new opportunities and mainly : saving my money…….
This post is the diary of how I made my Docker and Kubernetes playground at home using my old (and valiant) late 2009' Mac Mini.
As everybody I need dive deeply on new paradigms, patterns and products, test new solutions and I need a lab where build, deploy, destroy and measure…. in other words to play.
My main goals (with short answers):
I like the idea is that a project brings the whole development environment, in other words the projects has to be “battery included”.
I have worked with ‘VsCode’ for some time and I appreciate its flexibility but I also like it seems I am working with a slightly friendlier version of Vi or Emacs.
I need to implement a service with a lot of concurrency and parallelisms and since I wanted to do it for a while, I want to implement it in Go. …
I’ve spent much of the last decade avoiding Python but at the end I surrender…. Python met lot of my needs in term of quick prototyping, testing and systems management.
In add of this I still live with my laziness, source of another surrender.
These defeats lead me to looking for a comfortable, customizable and effective work environment.
In the last years I’ve worked with a lot of Python based framework/tool such Ansible or Locust, So build a Python environment where I like to dive become crucial.
Below a brief description, a collection of notes, written for personal use just to replicate and don’t loose what I did… once written, why don’t share this recipe? …
Since I read about microservices as “a way of designing software applications as suites of independently deployable services” I’m very intrigued by the docker and in the last six months I wondered what sorts out when we mix Consul and the last native swarm-mode.
Can we have a reliable system with less effort and less maintenance?
How could we have centralized key configuration and service discovery? Can the system self manages fault conditions and load variations?
I’ll try to show my point of view whit a practical (and implemented) solution for an extendible architecture. …