Google announces Firebase Genkit with Ollama support
ollama.com
ollama.com
This behavior is totally unacceptable and I am boycotting ollama and every ollama based stuff. I am not going to use ollama in my client projects anymore too.
And the acknowledgement was only added after community outcry. If not for that they would have kept on as if llama.cpp didn't exist.
Implying ollama has other back ends which it does not.
Just like Keybase, Bitwarden, Element, ggml also did.
- OpenAI - Groq - Anthropic - Cohere - Mistral
Check it out: https://github.com/TheFireCo/genkit-plugins
Besides, I am not sure what Genkit solves that cannot be done with an external provider. Can someone comment who is close to this technology?
Genkit appears to be an open source framework. It can connect to various LLM backends. This appears to be a plugin for connecting via that framework to a local Ollama instance. Nowhere is there a suggestion that they're providing managed Ollama VMs.
> Besides, I am not sure what Genkit solves that cannot be done with an external provider. Can someone comment who is close to this technology?
I use Firebase extensively for my side projects and worked at one YC startup that initially built on top of Firebase.To answer your question, what Firebase does particularly well is provide a really well-integrated full-stack development experience; one of the best ones, IMO. It's similar to Amplify on AWS which really just binds together multiple AWS backend services, but I find Firebase more pleasant to work with compared to Amplify. I would also make the case that it has some similarity to Azure Functions which skews more PaaS in its depth of integration than GCP Cloud Functions or AWS Lambda.
There's no reason any team couldn't just integrate with OpenAI or Llama3 on Together.ai or Fireworks.ai or run their own instance, but the DX on the Firebase platform is designed for teams to move fast and looking at the docs, I can appreciate the work the team put into making the experience feel seamless and reduce a lot of the repetitive code structures teams would otherwise have to build themselves to leverage the AI APIs.
Aside: I think Firebase is probably one of the best products out there for indie and weekend hackers building projects. The full-stack integration and local emulator are so well done and promote building with speed while still being scalable. The free credits are really generous and I run a ton of workloads in GCP for pennies. For some work, I'll drop into containers in Cloud Run and it still feels really easy to tie it all together. This is in contrast to working with Amplify, for example, which feels very "heavy" to begin with and then clunky as soon as you need to drop out into the underlying AWS infrastructure (ostensibly because CloudFormation is itself quite clunky).
I do a lot of solo building and Firebase lets me focus on just shipping stuff. In the last year alone, I've built at least 4 fully functioning products on Firebase (https://turas.app, https://coderev.app, https://usemeld.com, https://zeeq.ai); some with hundreds of users. It's a really productive platform.
Is Firebase at danger of being retired to the Google graveyard? I don't think so because fundamentally, Firebase is a set of wrappers around fundamental Google infrastructure (the same way Amplify wraps Lambda, DynamoDB, S3, etc.) so it wouldn't make sense to axe Firebase since it's just wrapping Cloud Functions, Firestore, Cloud Storage, etc.); it makes those services more accessible for application development. I could see them axing specific features of Firebase (which they have), but the core features that wrap infrastructure aren't at risk, IMO.