The hottest Microservices Substack posts right now

And their main takeaways
Category
Top Technology Topics

Demystifying API Gateways: What They Are & Why They Matter

Engineering At Scale • 72 implied HN points • 11 Feb 24
🕹 Technology APIs Microservices Architecture Security Performance
  1. API Gateway acts as an intermediary in microservices, handling client requests, and routing them to the appropriate microservices, simplifying communication for clients.
  2. API Gateway enhances security by authenticating and authorizing requests, provides rate-limiting to prevent attacks, and improves performance through caching and protocol conversion.
  3. Downsides of API Gateways include increased latency due to an extra hop, potential single point of failure, and added complexity to the system architecture.

Amazon Prime Video reduced costs by 90% by ditching Microservices [System Design Sundays]

Technology Made Simple • 159 implied HN points • 07 May 23
🕹 Technology System Design Microservices Architecture Scaling
  1. Amazon Prime Video saw a 90% cost reduction by moving away from Microservices to a monolith architecture. This change improved scalability and reduced infrastructure costs significantly.
  2. The challenges Amazon faced with their initial microservices implementation included hitting scaling limits and high overall costs of the system. Moving to a monolith architecture helped address these issues and allowed for better scaling.
  3. While the debate between Microservices and Monoliths continues, the decision should depend on factors like team size, emphasis on scale, and complexity. Microservices offer scalability but require careful planning, while monoliths are easier to design and manage.

Back-end for Front-end Pattern in Ecommerce

Cristian’s Substack • 39 implied HN points • 10 Apr 23
🕹 Technology Development Architecture APIs Microservices Patterns
  1. Back-end for Front-end (BFF) pattern helps reduce front-end complexity by acting as an interface between front-end and microservices/APIs.
  2. BFF pattern separates front-end requirements from back-end concerns, making the application easier to maintain and more resilient to API changes.
  3. Implementing BFF pattern can improve error handling, maintainability, and performance in an ecommerce platform by allowing for better control over API consumption and reducing network steps.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

How IFood Microservice handles 30k Requests per Second[Systems Design Sundays]

Technology Made Simple • 39 implied HN points • 23 May 22
🕹 Technology Systems Design Microservices Scaling Collaboration
  1. Develop solutions with future scaling needs in mind to make things easier down the line.
  2. Spend significant time planning how to divide responsibilities within your team to ensure efficiency and effectiveness.
  3. Clearly define your needs and anticipate potential problems to save time and effort in system design.

Middleware - Bringing observability up to speed

Termsheet by Attack Capital • 4 HN points • 04 Apr 23
🕹 Technology Observability AI Cloud Microservices Startup
  1. Founder Laduram Vishnoi's frustration with high costs of cloud observability tools led to the creation of Middleware.
  2. Middleware addresses challenges with traditional observability tools by offering a comprehensive and unified solution for cloud-native and microservices.
  3. Middleware uses AI-powered algorithms, is vendor agnostic, and correlates data from various sources to provide real-time observability and streamline issue debugging.

Some practical tasks with k8s Pods

DevCube • 2 HN points • 26 Feb 23
🕹 Technology Kubernetes Microservices Containers Development
  1. When working with microservices and Kubernetes, it's important to remember basic tasks like troubleshooting Pod startup and accessing logs.
  2. Don't solely rely on different tools for Kubernetes tasks, remember the fundamental basics.
  3. Appreciate foundational explanations like Liz Rice's video on containers, even if they are older, for understanding container technology.

Microservices impair the productivity of high performing programmers

Sheep Code • 1 HN point • 10 Aug 23
🕹 Technology Software Engineering Microservices System Design
  1. Microservices can limit the productivity of high performing coders due to the complexity of dependencies across teams.
  2. In a microservices system, expertise shifts from individual coding skills to system design and team collaboration.
  3. For a 10x engineer in a microservices environment, success is more about harmonizing microservices and teams than individual coding prowess.

Data is not a Microservice

Data Products • 1 HN point • 07 Jul 23
🕹 Technology Data Engineering Software Architecture Data Management Microservices
  1. Data requires a source of truth that microservices cannot inherently provide without a shift in software engineering practices
  2. Not all data is equally valuable, so treating all data as microservices can be costly and restrictive
  3. The data development lifecycle differs from software development, requiring flexibility, reuse, and tight coupling that conflict with typical microservices architecture

Operational Use case Patterns for Apache Kafka and Flink — Part 1

Tributary Data • 0 implied HN points • 03 Jan 23
🕹 Technology Data Platforms Stream Processing Microservices Data Management
  1. Operational use cases with Kafka and Flink are crucial for business operations due to their message ordering, low latency, and exactly-once delivery guarantees.
  2. Using polyglot persistency with different data stores for read and write purposes can help solve the mismatch between write and read paths in microservices data management.
  3. Implementing a backend rate limiter using Flink as a Kafka consumer can help prevent exhausting an external system (e.g., a database) due to high message arrival rates from Kafka.

Introducing Microservices

Overflow • 0 implied HN points • 29 May 23
🕹 Technology Microservices Architecture Scaling Communication Authentication
  1. Microservices architecture provides a solution to the challenges of monolithic applications by structuring an application as a collection of loosely coupled services.
  2. Transitioning from a monolith to microservices involves splitting different modules into independent services, offering flexibility in programming languages, databases, and scaling components of the application independently.
  3. Microservices offer benefits like continuous delivery, easy testing, fault tolerance, and better scalability compared to monolithic applications, making them a favorite among developers.

Searching for third-party details in a microservice architecture

Reflective Software Engineering • 0 implied HN points • 27 Oct 22
🕹 Technology Microservices Search Engine
  1. When developing a domain model, keep it concise with abstractions related to the problem being modeled. Consider how to handle search queries that involve third-party data not directly stored in the model.
  2. Avoid growing your domain model extensively to accommodate indirect relationships with third-party systems. This can lead to increased coupling, maintenance challenges, and data movements.
  3. Implement a solution using a CompositeKeywordProvider and asynchronous worker to fetch and manage keywords from various sources in a microservice architecture. Decouple keyword generation from data writing and searching, enabling a flexible and efficient search functionality.