Systems | Development | Analytics | API | Testing


Microapps vs. Microservices: the Similarities and Differences

From the end user’s perspective, the microapps and microservices often seem to provide the same functionality. However, development teams need to think about microapps vs. microservices when building products. Before you commit time to microapps or microservices architecture, take some time to consider how these options will affect user experience (UX), user interface (UI), and security of your websites, web apps, and mobile apps.

Secure Internal Microservice Authentication: A Comprehensive Guide

Internal microservice authentication is a critical component of software development. It ensures that only authorized users and services can access sensitive information and perform actions within a system. With the rise of microservices architecture and the increasing complexity of modern software ecosystems, implementing effective authentication mechanisms for internal microservices has become more important than ever.

Testing Microservices and Distributed Systems with JMeter

This blog post is about testing microservices and distributed systems with JMeter. It will focus on the principles of performance testing applications that are architected this way. We will not look at which JMeter samplers to use in order to generate a load against microservices or how to configure these samplers. This post will consider best practise and consideration in designing your performance testing when faced with these applications.

What is the Listen to Yourself Pattern? | Designing Event-Driven Microservices

The Listen to Yourself pattern is implemented by having a microservice emit an event to a platform such as Apache Kafka, and then consuming its own events to perform internal updates. It can be used as a solution to the dual-write problem since it separates Kafka and database writes into different processes. However, it also provides added benefits because it allows microservices to respond quickly to requests by deferring processing to a later time.

What is an API Gateway? A Complete Guide

An API’s main purpose is to allow multiple applications to communicate with one another. However, APIs can easily be made more secure and efficient through API gateways which provide a unified entry point across internal APIs. This unified entry point allows for greater control over user access and helps elevate API security measures like rate limiting while also applying security policies like OAuth or JWT. Plus, API gateways are extremely beneficial for securing microservices.

What is the Event Sourcing Pattern? | Designing Event-Driven Microservices

Event Sourcing is a pattern of storing an object's state as a series of events. Each time the object is updated a new event is written to an append-only log. When the object is loaded from the database, the events are replayed in order, reapplying the necessary changes. The benefit of this approach is that it stores a full history of the object. This can be valuable for debugging, auditing, building new models, and a variety of other situations. It is also a technique that can be used to solve the dual-write problem when working with event-driven architectures.

What is the Transactional Outbox Pattern? | Designing Event-Driven Microservices

The transactional outbox pattern leverages database transactions to update a microservice's state and an outbox table. Events in the outbox will be sent to an external messaging platform such as Apache Kafka. This technique is used to overcome the dual-write problem which occurs when you have to write data to two separate systems such as a database and Apache Kafka. The database transactions can be used to ensure atomic writes between the two tables. From there, a separate process can consume the outbox and update the external system as required.

What is the Dual Write Problem? | Designing Event-Driven Microservices

The dual write problem occurs when you try to write to two separate systems and need them to be atomic. If one write fails, and the other succeeds, you can end up with inconsistent state. This is an easy trap to fall into, and it can be difficult to avoid. We'll explore what causes the dual-write problem and explore both valid and invalid solutions to it.

Day 0 Service Mesh: A Simplified Approach for Building Microservices

The acceleration of microservices and containerized workloads has revolutionized software delivery at scale. However, these distributed architectures also introduce significant complexity around networking, security, and observability. As development teams grappled with reliability and governance issues, the service mesh pattern emerged to simplify management.

How To Build Scalable and Resilient Microservices | Microservices 101

Building scalable and resilient microservices requires an approach that eliminates the need to treat them as special. They should be treated as easily replaceable building blocks. This means eliminating bottlenecks and single points of failure but it can also mean changing from a pull-based approach to a push-based approach. CHAPTERS.