12x multiple for a Cloud SaaS company is not overpriced typically. I was surprised at this low multiple. Could be due to the current economic situation. And also the licensing changes, lack of product moat contributing in the wrong time.
On the performance side, there is definitely the N+1 problem which is solved (partially) by the data loader pattern.
But curious if the benefits vs tradeoffs is in favour of GraphQL?
And have you considered tools like Hasura/Postgraphile that take care of boilerplate CRUD APIs for databases? Then you actually just focus on writing business logic.
We have written a post[1] on building a real-time chat app with Streaming Subscriptions on Postgres. It gives a quick overview of the architecture used and how you can leverage the API on the client side with AuthZ. There’s a live demo that you all can try out.[2]
Interestingly, there are no breaking changes that were required to be addressed by Hasura GraphQL Engine to support Postgres 15. Hasura is fully compatible with this release, with the potential of adding the MERGE command via the GraphQL API soon.
Excited about the incremental performance improvements and making more secure defaults by revoking CREATE permission for public schema for non-superusers.
MERGE feature is interesting. But specifically on the revoking CREATE permissions for the public (or default) schema, this is a step in the right direction. Some of the defaults in Postgres can be more secure. For example, the first time I use a POSTGRES_PASSWORD to configure a password, changing this password involves more steps than just changing the values of the ENV, because it doesn't take the changed value there after.
Structured logging with JSON is going to improve a lot of debugging, again a great productive change.
Also, any idea when the docker image for Postgres 15 will be available?
Hasura connects to databases and all your other APIs to give a unified GraphQL API (and REST API, if you configure it).
This takes care of your CRUD APIs portion of building your app. With declarative Access Control Rules, you get powerful Authorization. IMO, these two should take care of 70% of your application code that you typically end up writing. The remaining will be custom business logic that you can write in any language or framework of choice and connect it to Hasura.
There’s of course more with the cloud offering to give you caching, rate limiting and monitoring in production. Hasura doesn’t host your database, it just needs the db connection string to get started.
We're very excited to launch GraphQL joins - a way for folks with existing investments in GraphQL to join data across GraphQL and non GraphQL sources. A few key points:
- Join data across new or existing GraphQL services: Your own GraphQL services or GraphQL vendor APIs (eg: Github)
- Join GraphQL services with other non-GraphQL services: Join data in your GraphQL Server with data in your databases (eg: Postgres, Timescale, Yugabyte with GraphQL servers)
- Uses native GraphQL with no changes to the GraphQL specification: No upstream changes are required to the GraphQL service
- Powered by semantic configuration - no custom code required.
Hey folks, I am Praveen, a developer advocate at Hasura. We first launched Hasura Learn in 2019 with the intention of building GraphQL tutorials for developers who wanted to learn GraphQL by getting hands-on, within the comfort of their favourite stacks. 2.5years later, we have grown this to just over 25 courses, added tutorials on databases, and Hasura (basics, authorization & production ready advanced concepts). We. have had a lot of help from the community in building & maintaining these over the years.
The intent has always been for devs to be able to get exactly the slice of info they need to get productive. The courses typically take between 30mins to about 2 hours to complete.
We're super excited to re-launch Hasura Learn today with it's brand new look, poised for many more courses to be added in collaboration with the community. We have also Japanese & Mandarin translations to our two most popular courses, and added 2 new databases courses (SQL Server & MySQL in addition to Postgres).
> with all your back end logic being in lambda functions.
Although this is recommended for NoOps and Scale, you can technically run all your backend logic on any full fledged servers that can run anywhere. Hasura just requires a HTTP endpoint for custom logic.
EXPLAIN ANALYZE output is cryptic enough for beginners to get any meaningful information out of it. Your thoughts on where to get started as a frontend developer?
How does one developing a product find out if they are infringing a patent?
Apart from the Apple/Samsung patent battle few years ago and to an extent Google/Oracle battle, I don’t remember anything in the tech space leveraging this.
Is there a list of companies that got screwed by giant companies because they unknowingly infringed a patent?
This is a misconception. Hasura doesn’t depend on serverless functions for doing business logic.
If you are comfortable writing GraphQL, you can add your own custom GraphQL server to Hasura for business logic.
If you are comfortable with REST APIs (or something that already exists), you can use Hasura Actions to define GraphQL types and call your REST endpoint to perform business logic.
Now where this server is hosted is totally upto the user. It can be serverless functions or can be a monolith server (in language of choice) hosted anywhere.
In India, we have this app called cure.fit[1] which now conducts live CrossFit classes for anyone to attend from home. This is just body weight movements and no equipment.
Claude Code works though. But now I can’t share this with non-technical users