Exploring Exposed: A Kotlin Solution to Database Access | Chantal Loncle
Вставка
- Опубліковано 16 вер 2024
- Recording brought to you by American Express. americanexpres...
Exposed is a database access library built with Kotlin that serves as an abstraction layer providing multiple database connectivity options. In addition to reducing the boilerplate code necessary to interface with a database, the library ensures type-safe SQL and reliable interactions as a seamless extension of a Kotlin developer’s code.
This talk ultimately seeks to provide Kotlin developers with a basic understanding of the current state of the Exposed library and its core functionality. We'll introduce the necessary configuration for a database connection, followed by an insight into the concept of transactions and their managers. We'll then examine schema definition, which will lead into an exploration of the different approaches for defining and manipulating relational data: the domain-specific language approach, the data access object pattern, and using plain SQL.
Lastly, to give perspective on the extended capabilities of Exposed, we’ll lightly touch on topics geared towards enabling a tailored developer experience, such as: user-defined column types and functions; custom extensions for controlled SQL query building; and statement lifecycle interceptors.
![*Next-door 10x Software Engineer* [FULL]](/img/n.gif)
Awesome presentation ! Love the library. Huge thanks to you, your team and all contributors 🎉
Good to see the progress on Exposed. I tried it years back, when it only had this one single developer, and when I understood the concepts it was a blast!
Looking so much forward to being able to observe data as Flows.
Great presentation! With coroutine’s support, it’s gonna be an awesome tool!
Required clear documentation with example project. I love Kotlin
Exposed is awesome! Close to native SQL with a nice Kotlin DSL
True, but at some point you are better off just writing native sql
Waiting for R2DBC support
Nice talk ... Exposed need some love
I will rerun some tests to ramp it up into production
I tried Exposed on Android as an alternative to Room. What can I say - I really loved the API, it's way more simple and idiomatic. Of course, Room being built specifically for Android still gives it considerable advantage on the platform, but man, all those annotations just don't feel right. To be fair, both have been a bumpy ride in some ways. I'm really excited that Exposed is consistently getting attention! Once it receives proper migration support, it may become a very viable competitor to Room. Also, I have a hunch that Exposed will have a strong leading position in KMM.
Since Room is now KMM compatible, what advantages do you personally experience when using Exposed compare to Room?
i fall in love with Kotlin. Best languange ever
creative syntax. i don't know kotlin can be written that way, wow.
comparison with Realm, SQLDelight and Room please. Why should we use this ? what are the advantages. Why should we care
It looks completely useless to me. SQLDelight is already multiplatform ready and has the perfect DSL. You should stop duplicating logic and stop being so useless
We love to see exposed in KMP as well with full auto migration support that works both on android and ios❤😊
Good job ! :)
Sounds good but I didn't see any reactivity when a query result changes. Any support for Flows like android Room?
It's not currently supported but they're working on it.
Great, but it would be cool to see a comparison with Hibernate also