Actix Web Documentation: Detailed documentation on using Actix-web, including examples and best practices for building web applications with Rust. - Source: dev.to / 2 months ago

Are you ready to embark on another journey in Rust? Today, we'll explore how to create a REST API that performs basic mathematical operations: addition, multiplication, and division. We'll use Actix, a powerful web framework for Rust, together with Rhai, a lightweight scripting language, to achieve our goal. - Source: dev.to / 3 months ago

Within actix-web, middleware is used as a medium for being able to add general functionality to a (set of) route(s) by taking the request before the handler function runs, carrying out some operations, running the actual handler function itself and then the middleware does additional processing (if required). By default, actix-web has several default middlewares that we can use, including logging, path... - Source: dev.to / 6 months ago

Rust is a popular system programming language, known for its robust memory safety features and exceptional performance. While Rust was originally a system programming language, its application has evolved. Now you can see Rust in different app platforms, mobile apps, and of course, in web apps — both in the frontend and backend, with frameworks like Rocket, Axum, and Actix making it even easier to build web... - Source: dev.to / 12 months ago

The actor-based web framework in Rust, Actix-web, is a game changer for developers looking for high-performance and scalable web applications. Actix-web's exceptional performance and concurrency capabilities enable developers to create robust and efficient web solutions. The framework's asynchronous request handling and non-blocking I/O provide impressive levels of concurrency, making it an excellent choice for... - Source: dev.to / about 1 year ago

While this may work for greenfield applications, I don't see this working well for preexisting schemas. From their getting started page: "Database fields are automatically created for any abstract getter methods", which definitely scares me away since they seem to be relying on automatic field type conversions. I prefer to manage my schemas when I can and do type and DAO conversions via mapper classes in the very... - Source: Hacker News / 9 months ago

Someone else mentioned jOOQ, but personally I also rather enjoyed JDBI3: https://jdbi.org/#_introduction_to_jdbi_3 It addresses the issues with using JDBC directly (not nice ergonomics), while still letting you work with SQL directly without too many abstractions in the middle. In combination with Dropwizard, it was pretty pleasant: https://www.dropwizard.io/en/stable/manual/jdbi3.html Other than that, I actually... - Source: Hacker News / 9 months ago

> I've been doing ORM on Java since Hibernate was new, and it has always sucked. Have you ever looked at something like myBatis? In particular, the XML mappers: https://mybatis.org/mybatis-3/dynamic-sql.html Looking back, I actually quite liked it - you had conditionals and ability to build queries dynamically (including snippets, doing loops etc.), while still writing mostly SQL with a bit of XML DSL around it,... - Source: Hacker News / 12 months ago

I found JDBi[1] to be a really nice balance between ORM and raw SQL. It gives me the flexibility I need but takes care of a lot of the boilerplate. It's almost like a third category. 1. http://jdbi.org. - Source: Hacker News / about 1 year ago

You could use something like jdbi or mybatis. It's not as ugly as raw jdbc and easier to use without all of the gunk from an ORM like hibernate. Source: about 1 year ago