bud VS ent

Yeah. It seems like Bud is the best option I have to get what I want: https://github.com/livebud/bud/

Hit me up if you have a longer time horizon and want to give https://github.com/livebud/bud a shot!

Awesome!

This would be such a game-changer for server-side rendering Javascript in Go with V8.

I'd love to integrate this into Bud[1].

[1] https://github.com/livebud/bud

I've also been seeing updates on this project, which is kind of preferring Svelte https://github.com/livebud/bud

https://github.com/livebud/bud - similar idea, but uses Svelte (a JS framework) to do the front end stuff. It’s smart enough to render the JS stuff on the server when possible, so you end up with the best of both worlds.

https://github.com/livebud/bud this framework is achieving SSR in go. Not Vue specifically last I saw, but maybe you can draw inspiration from what they did https://www.reddit.com/r/golang/comments/uoxocj/bud_the_fullstack_web_framework_for_go_developers/i8ke92h/?utm_source=reddit&utm_medium=web2x&context=3

See https://github.com/livebud/bud to learn more.

Just to clarify: Fymo is taking the same approach as Bud. See: https://github.com/livebud/bud/discussions/248 for details 🙂

An open-source GoLang project also took the same approach, livebud/bud.

I know how to create APIs. I actually don't wanna do an API link with the front end. You can check a framework built in GoLang, livebud/bud in Github. Seeking something like that, 'cause the project is still being developed.

In this article, we'll delve into the world of concurrency control in Go, specifically focusing on the optimistic locking approach. We'll explore its implementation using Ent ORM to illustrate how to manage data consistency when multiple users interact with the same resource. Keep in mind that this example serves as a simplified illustration, and real-world booking systems involve a many of additional complexities. However, the core concepts presented here provide a solid foundation for understanding optimistic locking in Go applications. Feel free to explore the complete source code in my GitHub repository for a more in-depth look at the implementation.

ent is a fairly recent ORM that uses a code-first approach where you define your schema in Go code. Ent is popular thanks to its ability to handle complex data models and relationships elegantly. It's statically typed, which can help catch errors at compile time. However, the learning curve might be steeper compared to more straightforward ORMs like GORM. It's a good fit for applications where complex data models and type safety are priorities.

If you found this article, than you are probably similar to how I was a few months ago. I started a project in Go that required a SQL backend and I wanted to use any tool that would help me build this backend quickly. I stumbled upon entgo (an ORM for Go) and decided to give it a try.

The ent orm for golang actually does some useful work for you. https://github.com/ent/ent

Backend Database interaction with entgo

You can use entgo.io for ORM stuff, it also has entgql extension that integrated with GQLGen. See more at the document: https://entgo.io/docs/tutorial-todo-gql