Skip to content

Introduction. Microservice Architecture. From Java EE To Cloud Native. Openshift VS Kubernetes

  1. Introduction
  2. Solution Architect. IT Architecture Frameworks
  3. Pets vs Cattle Analogy
  4. Service-Oriented Arhitecture vs Event-Driven Architecture
  5. Cloud Native
  6. Technical Debt
  7. Twelve-Factor Apps in Kubernetes
  8. Event Driven Architecture EDA
  9. Understanding the Differences Between Event-Driven, Message-Driven, and Microservices Architectures
  10. Multi-Tenancy Architecture
  11. Architecture Decision Records
  12. Self service developer platform
  13. Shift-Left
  14. Disaster Recovery
  15. SaaS
  16. Multi Cloud
  17. Cloud Automation
    1. Automation Glossary
  18. Microservices Best Practices and Design Patterns
  19. Microservice Patterns
    1. CQRS Pattern
  20. Microservices Anti Patterns
  21. Micro Frontend Architecture. Microservices for the Frontend
  22. Backends for Frontends
  23. Data Engineering
  24. Cloud Migration Checklist
  25. Microservices Failures
  26. Top Microservices Frameworks
  27. Transform Legacy Java Apps to Microservices with automation tools
  28. Namespaces for Data Structuring
  29. From SysAdmin to Architect
  30. Raft Consensus Algorithm
  31. PaaS
  32. Modular Monolith
  33. From Java EE To Cloud Native
  34. Monolith to Microservices Using the Strangler Pattern
  35. Openshift VS Kubernetes
  36. Career Path
  37. Full Stack Developer’s Roadmap
  38. Software Development Models
  39. Domain Driven Design DDD
  40. Software Development Tools
  41. vFunction. A system to transform monolithic Java applications into microservices
  42. Software in Automotive Industry
  43. Data Centers in Spain
  44. Bunch of Images
  45. Videos
  46. Tweets


Solution Architect. IT Architecture Frameworks

Pets vs Cattle Analogy

  • The History of Pets vs Cattle and How to Use the Analogy Properly
    • In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, itโ€™s all hands on deck. The CEO canโ€™t get his email and itโ€™s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, itโ€™s taken out back, shot, and replaced on the line.
    • Pets: Servers or server pairs that are treated as indispensable or unique systems that can never be down. Typically they are manually built, managed, and โ€œhand fedโ€. Examples include mainframes, solitary servers, HA loadbalancers/firewalls (active/active or active/passive), database systems designed as master/slave (active/passive), and so on.
    • Cattle: Arrays of more than two servers, that are built using automated tools, and are designed for failure, where no one, two, or even three servers are irreplaceable. Typically, during failure events no human intervention is required as the array exhibits attributes of โ€œrouting around failuresโ€ by restarting failed servers or replicating data through strategies like triple replication or erasure coding. Examples include web server arrays, multi-master datastores such as Cassandra clusters, multiple racks of gear put together in clusters, and just about anything that is load-balanced and multi-master.
  • Pets vs. Cattle: The Future of Kubernetes in 2022

Service-Oriented Arhitecture vs Event-Driven Architecture

Cloud Native

Technical Debt

Twelve-Factor Apps in Kubernetes

Event Driven Architecture EDA

Understanding the Differences Between Event-Driven, Message-Driven, and Microservices Architectures

Multi-Tenancy Architecture

Architecture Decision Records

Self service developer platform


Disaster Recovery


Multi Cloud

Cloud Automation

Automation Glossary

Microservices Best Practices and Design Patterns

Microservice Patterns

CQRS Pattern

Microservices Anti Patterns

Micro Frontend Architecture. Microservices for the Frontend

  • dzone: Micro Frontends With Example ๐ŸŒŸ Monolithic frontends are difficult to maintain, develop, test, and deploy. The solution is micro frontends. It is a type of architecture that can increase effectiveness and efficiency across teams.
  • Micro Frontend Architecture
  • dzone: Micro-Frontend Architecture The goal of this architecture is to see web applications as a composition of functionalities where each one is worked by independent teams.
  • Microfrontends: Microservices for the Frontend
    • Microservices are a popular way to build small, autonomous teams that can work independently. Unfortunately, by their very nature, microservices only work in the backend. Even with the best microservice architecture, frontend development still requires a high degree of interdependence, and this introduces coupling and communication overhead that can slow down everyone.
    • Can we take microservice architecture patterns and apply them to the frontend? It turns out we can. Companies such as Netflix, Zalando, and Capital One have pushed the pattern to the front, laying the groundwork for microfrontends. This article will explore microfrontends, their benefits and disadvantages, and how they differ from traditional microservices.

Backends for Frontends

Data Engineering

Cloud Migration Checklist

Microservices Failures

Top Microservices Frameworks

Transform Legacy Java Apps to Microservices with automation tools

Namespaces for Data Structuring

From SysAdmin to Architect

Raft Consensus Algorithm

  • The Raft Consensus Algorithm ๐ŸŒŸ etcd is a โ€œdistributed reliable key-value store for the most critical data of a distributed systemโ€. It uses the Raft consensus algorithm which was designed to be easy to understand, to scale, and to operate. The protocol and the etcd implementation were very quickly adopted by large distributed systems like Kubernetes, large distributed databases or messaging frameworks, where consensus and strong consistency is a must.


Modular Monolith

From Java EE To Cloud Native

Monolith to Microservices Using the Strangler Pattern

Openshift VS Kubernetes

Career Path

Full Stack Developer’s Roadmap

Software Development Models

Domain Driven Design DDD

  • dzone: The Concept of Domain-Driven Design Explained In this article, we define the core concepts around domain-driven design, explain them, and highlight the advantages and downsides of the approach.
    • Using microservices means creating applications from loosely coupling services. The application consists of several small services, each representing a separate business goal. They can be developed and easily maintained individually, after what they are joint in a complex application.
    • Microservices is an architecture design model with a specific bounded context, configuration, and dependencies. These result from the architectural principles of the domain-driven design and DevOps. Domain-driven design is the idea of solving problems of the organization through code.
    • The business goal is important to the business users, with a clear interface and functions. This way, the microservice can run independently from other microservices. Moreover, the team can also work on it independently, which is, in fact, the point of the microservice architecture.
    • Many developers claim microservices have made them more efficient. This is due to the ability to work in small teams. This allows them to develop different small parts that will later be merged as a large app.
    • They spend less time coordinating with other developers and more time on developing the actual code. Eventually, this creates more value for the end-user.
  • DDD โ€” Events Are Complex Why do Events matter so much in Domain-Driven Design?

Software Development Tools

vFunction. A system to transform monolithic Java applications into microservices

Software in Automotive Industry

Data Centers in Spain

Bunch of Images

Click to expand!

microservices infographic

you dont need kubenetes

sw consumers

Openshift SaaS VS Kubernetes SaaS

Openshift VS Kubernetes

Kubernetes on its own is not enough

how mature is your microservices architecture

bytebytego microservice tech stack


Click to expand!


Click to expand!