Systems | Development | Analytics | API | Testing

Microservices

Microservice Pitfalls: Solving the Dual-Write Problem | Designing Event-Driven Microservices

When building a distributed system, developers are often faced with something known as the dual-write problem. It occurs whenever the system needs to perform individual writes to separate systems that can't be transactionally linked. This situation creates the potential for data loss if the developer isn't careful. However, techniques such as the Transactional Outbox Pattern and Event Sourcing can be used to guard against the potential for data loss while also providing added resilience to the system.

Tackling Microservices Testing Challenges: Effective Mitigation Strategies

According to Statista, the microservices architecture market will grow at a robust CAGR of 19.6%, reaching $10.86 billion by 2027, up from $4.44 billion in 2022. The shift to microservices architecture has revolutionized software design and development, significantly enhancing agility, scalability, resilience, delivery times, cost-effectiveness, and more. Since Dr.

Defining Asynchronous Microservice APIs for Fraud Detection | Designing Event-Driven Microservices

In this video, Wade explores the process of decomposing a monolith into a series of microservices. You'll see how Tributary bank extracts a variety of API methods from an existing monolith. Tributary Bank wants to decompose its monolith into a series of microservices. They are going to start with their Fraud Detection service. However, before they can start, they first have to untangle the existing code. They will need to define a clean API that will allow them to move the functionality to an asynchronous, event-driven microservice.

Event-Driven Microservices in Banking and Fraud Detection | Designing Event-Driven Microservices

How do we know whether Event-Driven Microservices are the right solution? This is the question that Tributary Bank faced when they looked at modernizing their old fraud-detection system. They were faced with many challenges, including scalability, reliability, and security. Some members of their team felt that switching to an event-driven microservice architecture would be the magic bullet that would solve all of their problems. But is there any such thing as a magic bullet? Let's take a look at the types of decisions Tributary Bank had to make as they started down this path.

7 Key Benefits of Microservices

Jeremy H - May 20, 2024 In the age of technology, businesses are experiencing a digital renaissance. Customers are interacting with companies through mobile devices and social media platforms more than ever, and they expect a higher level of service. This has forced businesses to re-evaluate how they operate to meet customer demands. One such way companies are changing the way they work is by adopting the benefits of microservices. The question is, why are microservices so helpful to modern enterprises?

Most Prolonged Interaction With the Microservices Conversion

Back in the 2000s, code lived in one execution thread. Database queries, user interactions, and data pipelines were all managed by the same processes. The problem? Everything was interconnected and interdependent. Fixing one thing might break another. Releases were all or nothing. We call this monolith hell. Your ticket out? Microservices.

Monolith to Microservices: Key Takeaways for the Switch

Back in the 2000s, code lived in one execution thread. Database queries, user interactions, and data pipelines were all managed by the same processes. The problem? Everything was interconnected and interdependent. Fixing one thing might break another. Releases were all or nothing. We call this monolith hell. Your ticket out? Microservices.

Resolving Database Conflicts with Centralized APIs in Microservices

Back in the 2000s, code lived in one execution thread. Database queries, user interactions, and data pipelines were all managed by the same processes. The problem? Everything was interconnected and interdependent. Fixing one thing might break another. Releases were all or nothing. We call this monolith hell. Your ticket out? Microservices.