Temporal Reviews

Fluper Reviews

1. Zainab Rashid

   · COO at ClickMyLoan · about 2 years ago
   Our company offers a cutting-edge mobile banking app, connecting customers with secure and convenient digital banking services.

   In collaboration with Fluper, our primary objective was to develop a user-friendly mobile banking app, allowing customers to manage accounts, make payments, and access financial information. Key deliverables included a seamless user interface, robust security features, and real-time transaction tracking.

   🏁 Competitors: Chime

   👍 Pros:    What truly impressed us about fluper was their commitment to ensuring top-tier security for the mobile banking app. they seamlessly integrated advanced security measures and compliance with banking regulations, providing customers with a secure and convenient digital banking experience.

   👎 Cons:    Fluper was largely positive for us. they played a pivotal role in enhancing post-launch support, providing excellent financial analytics, and ensuring the long-term success of our mobile banking app.
2. Eslam Tawakol

   · QA Manager at Flipdish · about 2 years ago
   Our company offers a comprehensive restaurant management platform, connecting restaurant owners with tools for reservation management, order processing, and customer engagement.

   In collaboration with Fluper, our primary goal was to create a user-friendly restaurant management software that allowed owners to streamline reservations, process orders, and interact with customers. Key deliverables included a responsive interface, secure data storage, and real-time performance analytics.

   🏁 Competitors: JustFoodERP, Foodservice Suite

   👍 Pros:    What truly impressed us about fluper was their deep understanding of the restaurant industry's intricacies. they seamlessly integrated features that enhanced table management and customer interactions while ensuring data security and compliance with industry standards.

   👎 Cons:    Fluper exceeded our expectations. they played a crucial role in enhancing post-launch support, providing excellent restaurant analytics, and ensuring the long-term success of our restaurant management platform.
3. Levi Hernandez

   · COO at Momentus Technologies · about 2 years ago
   Our company provides a comprehensive event management platform, connecting event organizers with tools to plan, promote, and execute successful events.

   Partnering with Fluper, our goal was to develop an event management software that offered features for event planning, ticketing, and attendee engagement. Key deliverables included a user-friendly event dashboard, secure payment processing, and real-time analytics.

   🏁 Competitors: Event Management Technology

   👍 Pros:    What truly set fluper apart was their deep understanding of the event industry's intricacies. they seamlessly integrated features that streamlined event planning and promotion while ensuring data security and compliance with industry standards.

   👎 Cons:    Fluper exceeded our expectations. they played a pivotal role in enhancing post-launch support, providing exceptional event analytics, and helping us transform our event management capabilities.

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 16 days ago

• Your Agent Bills While It Waits. Here's the Fix.

  Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 22 days ago

• Compiler as Custodian

  Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 2 months ago

• How we turned our workflow editor into a real SDK

  We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 2 months ago

• Three days debugging a missing trace

  The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago

Fluper mentions (0)