Automation in Microservices is another key design principle for our architecture, and the main thinking behind this is to use tools for automated hosting, testing, and deployment. Let’s deep dive in different automation strategies. On-Demand Hosting By automated hosting, we mean once we have our software architecture perfected, i.e. our production environment perfected, we want […]
Microservices Design Principle: Automation Read More »
Observability Design Principle is key for our microservices architecture because this architectural style gives you an architecture which is complex with many moving parts. Therefore, we need the ability not only to see the health of our workflows, i.e. our logical transactions, but we also need the ability to see the health of all our
Microservices Design Principle: Observability Read More »
Resiliency design principle of mircroservices is all about making our software reliable and available and ensuring that if we do have any failures within our back‑end microservices, each service fails fast and there’s alternate functionality so that the user doesn’t face any disruption. Let’s discuss the various steps to develop a resilient system Design for
Microservices Design Principle: Resiliency Read More »
The aim of Domain-driven Cohesion in Microservices is to help us tightly scope our microservices so that they represent a specific business domain within our organization in terms of the data and the functionality they provide. The cohesion part of this principle is just there to emphasize the fact that each individual microservice must be
Microservices Design Principle: Domain-driven Cohesion Read More »
Autonomy in microservices refers to the degree of independence and self-sufficiency that each individual microservice possesses within a microservices architecture. This enhances the performance and reliability of the service and gives consumers more guarantees about the quality of service they can expect from it. Coupled with statelessness, autonomy also contributes to the overall availability and scalability
Microservices Design Principle: Autonomy Read More »
Java 17 introduced enhancements to the Pseudo-Random Number Generators (PRNGs) to make working with random numbers in Java more versatile and user-friendly. These improvements provide better support for using multiple PRNG algorithms and properly handling stream-based operations. Here’s an overview of the enhancements: 1. PRNG Enhancements: Java 17 introduces a new interface type called RandomGenerator
Pseudo-Random Number Generators Read More »
Java 17 LTS is the latest release providing long-term support for the Java SE platform. According to the Oracle No-Fee Terms and Conditions License, JDK 17 binaries are permissible for use in production and can be redistributed without any associated costs. The abbreviation “LTS” denotes “long-term support,” and this release is slated for availability on
Java 17: A Brief Overview of Features and Enhancements Read More »
In the Visitor pattern, we employ a visitor class to alter the execution algorithm of an element class. This flexibility allows the element’s execution algorithm to adapt as the visitor changes. This pattern falls under the behavior pattern category. In accordance with this pattern, an element object must accept the visitor object, enabling the visitor
The Template Method is a behavioral design pattern that defines a blueprint for an algorithm in a superclass but allows specific steps of the algorithm to be overridden by subclasses without changing its core structure. Consider developing a data mining application that analyzes corporate documents in various formats (PDF, DOC, CSV) to extract meaningful data.
The Strategy pattern, also known as Policy is a design pattern that allows you to define a range of methods for achieving a specific task and place each method in its own class. These classes, known as strategies, are interchangeable, providing flexibility in algorithm selection without altering the core code. Imagine you’re developing a navigation
