Community Picks·3yMicroservices VS Monoliths
Microservices VS Monoliths. Microservices need no introduction and…. Microservices are a de facto solution for a web application which enables organizations to get most benefits of the cloud. The answer is not a perfect black and white scenario and its not a one-size-fits all solution.
ByteByteGo·3yEP67: Top 9 Microservice Best Practices
QA Wolf will get your web app to 80% automated end-to-end test coverage in just 4 months. QA Wolf offers a 90-day pilot so you can try them out. Kubernetes Periodic Table sheds light on the 120 crucial components that make up the KuberNETes ecosystem.
Cloud Native Daily·3yMicroservices Patterns: Event Sourcing
Event Sourcing is a different way of structuring the business logic and persisting aggregates. It persists an aggregate as a sequence of events and each event represents a state change of the aggregate. It helps to preserve the history of aggregates, which is valuable for auditing and regulatory purposes.
JavaScript in Plain English·3yRedis vs Kafka vs RabbitMQ
Redis vs Kafka vs RabbitMQ will compare the three most popular brokers: RabbitMQ, Kafka and Redis. RabbitMQ supports all major languages, including Python, Java,.NET, PHP, Ruby, JavaScript, Go, Swift, and more. Kafka Scale: can send up to a million messages per second.
Amplication·3yDifferences in Scaling Stateless vs. Stateful Microservices
A microservice is designed, developed, and deployed as an independent service. Stateless microservices maintain and manage session-specific states throughout multiple requests. Scaling out involves the addition of more nodes (or instances) of your microservice. It's important to understand that scaling out is done automatically in a serverless environment.
Cloud Native Daily·3yMicroservices Patterns: Business Service Patterns
Hexagonal Architecture is an architectural pattern used in software architecture design. It aims at creating loosely coupled application components that can be easily connected to their software environment by means of ports and adapters. In this blog, I will try to emphasize those differences by revisiting some of the core design patterns and principles built into each architecture.
Community Picks·3yOptimizing Your Architecture with Microservices Design Patterns
Optimizing Your Architecture with Microservices Design Patterns. We will explore the need for design patterns, popular patterns, and the importance of avoiding anti-patterns. These patterns provide guidance and best practices to overcome common problems such as service communication, data management, fault tolerance, and scalability.
Cloud Native Daily·3yAPI Latency in Microservices
API Latency in Microservices is critical since it directly impacts Microservices’ responsiveness and scalability, says Lahiru Hewawasam. Latency is the time taken for data to travel from one point to another. If one service takes too long to respond, it could lead the requesting service to time out.
Amplication·3yServerless vs. Containers for Microservices: What should you choose
Serverless vs. Containers for Microservices: What should you choose? Amplication has just surpassed the remarkable milestone of 11,000 stars on GitHub! We'll explore the strengths and weaknesses of Containers and Serverless for building microservices while exploring various use cases to help determine their suitability.
Cloud Native Daily·3yMicroservices Patterns: Service Discovery Patterns
A Service Registry is a centralized server / a database containing the location of service instances. In a microservices setup, services update their locations in the Service Registry at regular intervals. Service consumers can connect to the service registry and fetch the locations of those services. This will help the client to know where the service instance is located.
Cloud Native Daily·3yMicroservices Patterns: The Saga Pattern
This blog will give the reader some insights into ACID Transactions, 2PC Pattern and finally the Saga Pattern. The primary objective is to give an overview of how Saga Pattern operates and how it can solve real-world distributed transactional issues. The blog was written with some background reading on multiple literature resources mentioned under the References.
DZone·3yDocker Alternatives
DZone will explore the Docker alternatives to your SaaS application. Join the DZone community and get the full member experience. Join For Free Docker technology has revolutionized the infrastructure management landscape in such a way that Docker has now become a synonym for containers.
Cloud Native Daily·3yRethink the Way You Share Data Between Microservices with Change-Data-Capture
Re -Think the Way You Share Microservices Data. Use Change Data Capture to replicate the data for microservice architecture. Re-think the way You Share Data Between Microservices with Change-Data-Capture Organizing and sharing your data across microservices. Use the replication system when the services will be sharing the data.
Cloud Native Daily·3yAdvanced Postman Techniques: Unlocking Hidden Gems for API Testing
Unsplash Postman, the popular API testing tool, has become a staple in the software development community. It offers a user-friendly interface for making API requests and automating tests. Many users are unaware of the advanced features and techniques available in Postman that can significantly enhance their API testing workflows.
Cloud Native Daily·3y3 Ways to Reproduce Issues in Microservices
The first thing we want to be able to do is reproduce errors and issues. By reproducing errors, we can confirm it’s a recurring issue, rather than a sporadic one, and that it requires a fix to ensure that our product is working properly. We will show how to reproduce issues in three different ways.
