Using serverless architecture for microservices in customer journeys presents several distinct challenges. One significant hurdle is observability and debugging across distributed, ephemeral functions, making it difficult to trace user flows and identify bottlenecks in a complex journey. State management also becomes critical, as maintaining user context and progress across stateless serverless invocations requires external data stores and careful design. Furthermore, cold start latency can negatively impact the real-time responsiveness expected in a seamless customer experience, especially for less frequently accessed microservices. Orchestrating these independent functions to ensure a cohesive and consistent journey introduces increased architectural complexity, requiring robust event-driven patterns and error handling mechanisms to prevent disruptions. Finally, managing costs can be tricky due to the pay-per-execution model, making cost predictability a concern for highly variable workloads. More details: https://www.dsl.sk/article_forum.php?action=reply&forum=255549&url=https://infoguide.com.ua/