Spark Framework Reviews

Temporal Reviews

Spark Framework mentions (29)

• Indexing All of Wikipedia on a Laptop

  The code for serving queries is found in the WebSearch class. We’re using Spark (the web framework, not the big data engine) to serve a simple search form:. - Source: dev.to / about 2 years ago

• [ Servlet + JSP + JDBC ]

  Get a solid grasp of building web applications with Java either using Spring (using Spring Boot) or Spark (if you're also new to Java learning Java and Spring can be a mouthful). Instead of JSP use something Thymeleaf or build the frontend with HTML and JavaScript (and serve the bundles). Source: over 2 years ago

• What's the language of the startup?

  So most of the "tech" stack goes out. In our first startup we created our own web-container by using https://sparkjava.com - and then built a JSR-223 scripting support. Source: over 2 years ago

• What side-projects did you work on during your university years?

  Stack: Java, Spark (not the Apache Spark but this), Kafka, several other libraries like FasterXML's Jackson. Source: about 3 years ago

• Full Time

  The blog is just hugo so it's 100% static files over nginx. The search engine is serverside-rendered mustache templates via handlebars[1], via served via spark[2]. It's basically all vanilla Java. I do raw SQL queries instead of ORM, which makes it quite a bit snappier than most Java applications. The sheer size of the database also mandates that basically every query is a primary key lookup. The code is written... - Source: Hacker News / about 3 years ago

Temporal mentions (16)

• 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 / 4 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 1 month 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 / about 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 / 3 months ago

• Best ChatGPT Alternatives in 2026: Evaluated on Automation, Persistence, and Data Ownership

  A typical production stack for teams using Claude or Gemini as the reasoning layer includes an LLM provider API, an orchestration layer (n8n, Temporal, or a custom Python service), application infrastructure (a server running the orchestration code), and a data layer (a database for storing results). Each boundary introduces a failure point. When the LLM provider changes its rate limits, as OpenAI did repeatedly... - Source: dev.to / 4 months ago