Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Upstash Workflow! 🎉 Write robust, error-resistant serverless functions by default: ◆ No serverless timeouts ◆ Supports hour-long API requests ◆ Automatic retries on failure ◆ Delivery guarantees, batching & more 90-second demo 👇

58,296 просмотров • 1 год назад •via X (Twitter)

Комментарии: 9

Фото профиля Upstash
Upstash1 год назад

Monitor all of your workflows in one intuitive dashboard. See which workflows are running, which succeeded, or exactly why a workflow failed.

Фото профиля Upstash
Upstash1 год назад

If you want to build robust serverless apps that users love using - try out Upstash Workflow. Documentation:

Фото профиля Steven Tey
Steven Tey1 год назад

"except Angular – you gotta draw the line somewhere" 💀😆

Фото профиля Fredkisss is on 🦋 blue sky 🦋
Fredkisss is on 🦋 blue sky 🦋1 год назад

So… @inngest 2.0 ?

Фото профиля Richard Poelderl
Richard Poelderl1 год назад

I had a severe performance issue for one of my apps with inngest because there’s a http req/res for every step which took like 1s for each step. App hosted in Germany — do you know how your latency will compare? Do you have servers in Europe to notify about the step executions?

Фото профиля villainy
villainy1 год назад

so a 1v1 copy of

Фото профиля Shubham Singla
Shubham Singla1 год назад

There is a bug inside nextjs workflow package. It does not run failureFunction on the failure. Also our app is hosted in Australia, qstash client average response time is 800ms.

Фото профиля Jordan
Jordan1 год назад

Very niceeee

Фото профиля Andrew
Andrew1 год назад

Pricing is a little unclear. I see a page in the docs for pricing but anyway you could give some real world examples there too? If I'm understand correctly though, the attached simple example from the docs, would be 2 QStash messages?

Похожие видео

QVAC SDK 0.15.0 is live. This release adds multiple prompts batching, brings a native AMD GPU backend to the stack, moves more vision encoders onto mobile GPUs, and adds a second local coding-agent integration. Main highlights: - Prompt batching for the LLM addon. Batch multiple prompts into one job and process them concurrently, with each answer returned the moment its generation finishes. - Native AMD GPU backend. A first-class HIP/ROCm backend in @qvac/vla-ggml, auto-selected over Vulkan with clean fallback when ROCm is absent. - A second local coding agent. OpenClaw joins OpenCode for local, cloud-free agent workflows. AGENTS - OpenCode plugin update (@qvac/opencode-plugin). Aligned with the current SDK, CLI, and AI SDK provider packages. A fresh install runs OpenCode against managed local QVAC models out of the box, from the default qvac/qwen3.5-9b, with no manual qvac serve setup. - OpenClaw plugin (@qvac/openclaw-plugin). A second coding-agent integration alongside OpenCode. A fresh setup installs the plugin, creates a local qvac provider through onboarding, and runs a QVAC model through OpenClaw🦞's local service path. LANGUAGE MODELS - Prompt batching (LLM addon). Batch multiple prompts in one job and run them concurrently, each answer returns the moment its generation finishes, no waiting on the others. - Reasoning-context trimming on hybrid + recurrent models (@qvac/llm-llamacpp). remove_thinking_from_context now works beyond pure-attention models. Same JS API, no throw. VOICE AND SPEECH - Transcription (transcription-parakeet 0.9.0). More robust CPU fallback on GPU failure and a faster Vulkan backend on Pixel 9. - Text-to-speech features (tts-ggml 0.4.0). Adds LavaSR for noise removal and adjustable output frequency up to 48 kHz, plus Japanese via Chatterbox. - Text-to-speech fixes (tts-ggml 0.4.1). CPU fallback on GPU failure, a q8_0 KV crash fix on Metal with Chatterbox. VISION - Qwen3.5 vision encoder on GPU (Android). Image encoder moves onto the phone GPU, with a smarter tile-grid preprocessor and default image-token caps, for flagship Android: Vulkan on Mali (Pixel 9 Pro) and OpenCL on Adreno 830 (Galaxy S25). - Gemma-4 vision encoder on GPU (Android). Vision encoder runs on the phone GPU instead of CPU, same flagship Android targets. PLATFORM AND PERFORMANCE - AMD GPU backend (@qvac/vla-ggml). Native HIP/ROCm backend, auto-selected over Vulkan with clean fallback when ROCm is absent (Linux x64 only). Comes with ~23% faster than Vulkan, ~14% faster than PyTorch-ROCm, parity preserved. Unified code style. A cleaner, more consistent, easier-to-contribute codebase. Let's build. npm install @qvac/sdk

QVAC

17,700,244 просмотров • 7 дней назад

I built an agent that answers machine-learning questions. It's autonomous, and the best part is that I built the whole thing without writing a single line of Python code. Here is what I did and how I did it: Over a year ago, a friend and I built a site that publishes multi-choice questions. You get a new one every day. I decided to have GPT-3.5 answer questions. Here is what I needed to build: 1. Connect to the site's API to retrieve today's question 2. Extract the question and the potential choices 3. Connect to OpenAI's API and ask GPT-3.5 to answer the question 4. Parse the answer from the model 5. Submit the answer back to the API to get the score Not difficult. Likely several hours of work. But I didn't have to write any code. I built the whole thing by dragging and dropping components using Vellum is a YC-backed platform for developers to build LLM applications. They are the only ones I've seen offering this functionality. They sponsored this post, and their team helped me with all my questions while I built this. I created a workflow. The platform supports several node types to build whatever you have in mind. I show how I put the whole thing together in the attached video. The only code I had to write was a few lines of Jinja to parse and transform the API and the LLM results. There are three lessons I want to share from this experience: First, the best possible code is the one you didn't write. I'm a big fan of no-code tools because they help me materialize my ideas fast. They help product people, designers, and no coders collaborate on the solution. Second, Large Language Models are sensitive to how you prompt them. Small changes to prompts can make a big difference in results. This is more pronounced when you are building a multi-step workflow. Third, automated testing and evaluation for prompts is critical. There aren't many companies thinking about this. They'll have a hard time moving from a demo phase. The attached video will show you what I did.

Santiago

309,825 просмотров • 2 лет назад

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,363 просмотров • 3 месяцев назад

For over a year, Jeremy Howard has been in stealth mode. In this exclusive talk, he showcases what he's been working on. He & Jonathan Whitaker show us SolveIt, a new dev environment and programming paradigm. 🤯 Imagine this workflow: - Build a web app & interact with its UI on the same screen as your code. No more flipping to a separate browser. - Use live variables from your REPL directly in prompts to the AI. The AI knows your current state. - Turn any Python function into an AI tool instantly. No no registering tools or MCP. Just write a function in a cell and tell the AI to use it. This is a live, malleable environment that fuses the best ideas from Literate Programming (Knuth), the live-object world of Smalltalk, and the interactive cells of Jupyter. Who is Solveit for? Jeremy's take: SolveIt is best for programmers who are either very new ( 20 years). Why? Because developers in the middle (3-20 years) often have ingrained workflows and can find this different paradigm confronting. New devs are open-minded and build good habits from scratch, while veterans immediately recognize how this approach solves decades-old problems of complexity and state management. My Thoughts It's early days, but it is super cool. You get all the fun of trying a new programming language without learning new syntax (Python), because it will show you new patterns and ways of doing this. If you are wiling to climb the learning curve it is an extremely powerful tool that you can be productive with on real tasks like writing and coding. I'm personally addicted to it for several workflows and am afraid of losing it tbh. How Can You Try It? Just follow Jeremy Howard - he will announce something in the coming weeks or months (I suspect if this post is popular he might do something soon 🤣 ) TIMESTAMPS (00:00:00) - Introduction (00:00:30) - The SolveIt Method vs. "Vibe Coding" (00:04:00) - Investing in Yourself: Long-Term Skill Building (00:07:45) - Software Engineering vs. Short-Term Gains (00:12:15) - The Problem-Solving Loop: Understand, Plan, Implement, Review (00:18:50) - Example: Literate Programming with the Claudette Library (00:24:15) - First Look at the SolveIt Environment (00:28:34) - Demo Start: Building an Eval for Multimodal Models (00:31:16) - Iterative Development: Exploring the iNaturalist API (00:39:15) - Catching Bugs Instantly by Working Step-by-Step (00:43:37) - Prompting LLMs with Structured Outputs (00:51:54) - Demo: Building a Live Web App Inside SolveIt with FastHTML (01:00:24) - Demo: Exploring a Complex API (Cloudflare) (01:08:45) - Creating Custom AI Agent Tools with Zero Boilerplate (01:19:00) - SolveIt Ergonomics: Modes, Secrets, and Keyboard Shortcuts (01:28:30) - The Power of the SolveIt Community (01:30:45) - Who Should Use SolveIt? (01:34:30) - This is Just the Tip of the Iceberg YT Video and links in reply

Hamel Husain

111,916 просмотров • 11 месяцев назад