news.livebook.devLivebook.dev - The Livebook Blog

The Livebook Blog Back to Homepage Subscribe to Updates Labels All Posts releases tutorials announcements launch week Jump to Month March 2024 October 2023 August 2023 July 2023 April 2023 March 2023 February 2023 January 2023 December 2022 October 2022 September 2022 August 2022 July 2022 May 2022 January 2022 April 2021 Powered️ by Create yours, for free! announcements a month ago Welcoming Tigris as a new sponsor of Livebook! We’re thrilled to announce Tigris as the latest Livebook sponsor! Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world. We’ve prepared a short demo showcasing the Tigris API through Livebook (of course ?) to highlight its capabilities. Quick intro to Tigris You’ll find Tigris intuitive if you’re familiar with other object storage services like AWS S3. Here’s an example of saving an object to a Tigris bucket: ExAws.S3.put_object( "my_tigris_bucket_name" , "cat.jpeg" , image) | ExAws.request!() Notice we’re using an AWS S3 client. Thanks to Tigris’s S3-API compatibility, transitioning your code requires minimal changes. Let’s say the object is uploaded to a public bucket; to retrieve it, it’s just a simple HTTP GET: object_url = "https://fly.storage.tigris.dev/my_tigris_bucket_name/cat.jpeg" Req.get!(object_url) Simple, right? Now for the real game-changer… Imagine uploading a file from São Paulo (Brazil). The object is stored automatically in the nearest Tigris region, GRU (São Paulo). When a user in Mumbai (India) requests the object, it’s initially served from GRU. However, Tigris automatically caches the object in the region closest to the request’s origin, significantly improving subsequent access times — all without extra configuration! Here are some real numbers for that example: Request Response Response time (milliseconds) gru (São Paulo) gru (São Paulo) 3.018 bom (Mumbai) gru (São Paulo) 1207.364 bom (Mumbai) sin (Singapore) 141.98 bom (Mumbai) sin (Singapore) 134.972 bos (Boston) gru (São Paulo) 1393.971 bos (Boston) iad (Washington, D.C.) 29.399 bos (Boston) iad (Washington, D.C.) 21.344 Tigris combines object storage with CDN capabilities. That means great UX for end-users and great DX for developers. Let’s look at a demo notebook that showcases this. Demo In our demo, we use Livebook’s integration with MapLibre to plot the HTTP request and response locations on a map. We also log the response times in a table . Additionally, we leveraged the Livebook Apps feature to visualize the notebook as an app. Here’s the result: Wrap-up Tigris brings some cool innovations to the object storage space. For example, here’s how you could use it as a global key-value store from Elixir . If you want to try using Tigris with Elixir, they have official Elixir support . releases launch week 7 months ago Vim and Emacs key bindings - Launch Week 2 - Day 5 Welcome to the 5th day of Livebook Launch Week 2! ? For those of us who found ourselves instinctively trying to use Vim or Emacs shortcuts in Livebook, only to realize that these weren’t supported, feeling frustrated. We hear you. We’re excited to announce that now you can use Vim and Emacs key bindings while coding in Livebook. Let’s see how it works. Using Vim or Emacs key bindings in Livebook Go to the settings page in Livebook and choose the Key bindings” you prefer: Once that’s done, you can use it in any Livebook cell with a code editor, like in a code cell or a markdown cell. Here’s an example using Vim keybindings: From now on, you can bring your Vim/Emacs muscle memory to Livebook for a more pleasant and productive experience. Thanks to Kenichi Nakamura , who contributed that feature . What now? To start using that new feature, install the latest version of Livebook and have fun! More of Launch Week 2 Day 1: Remote execution Smart cell Day 2: Speech-to-text with Whisper: timestamping, streaming, and parallelism, oh-my! Day 3: Introducing File Integration Day 4: Integration with SnowFlake and Microsoft SQL Server And if you want to discover everything that was added/changed in this release, here’s the changelog . releases launch week 7 months ago Integration with Snowflake and Microsoft SQL Server - Launch Week 2 - Day 4 Welcome to the 4th day of Livebook Launch Week 2! ? Today’s post is about our two new database integrations: Snowflake and SQL Server. Together with those new ones, Livebook now comes with built-in integrations for seven databases and data warehouses : PostgreSQL MySQL SQL Server SQLite Google BigQuery Amazon Athena Snowflake Let’s see how the new integrations work. Connecting to Snowflake The Snowflake integration is available through the Database Connection Smart cell. All you need to do is configure the Smart cell with your connection credentials, and you’ll be ready to start executing queries. Let’s see how that works. Under the hood, this is different from the other database integrations we already have. Livebook connects to Snowflake through ADBC (Arrow Database Connectivity), using the ADBC hex package , which contains ADBC bindings for Elixir. The Arrow format is highly efficient, and it’s also integrated with Explorer, so now you can easily query a database and load the result into an Explorer dataframe . Good news for those of us doing data analysis with Elixir and Livebook. ? Connecting to Microsoft SQL Server Connecting to SQL Server is also super simple. All you need to do is add a new Database Connection Smart cell, select SQL Server, and fill in your database credentials. Here’s how it works. This was a community contribution from Simon McConnell . Curious fact: the pull request contains less than 250 LOC! Cool, right?! ? What now? To start playing with those new features, install the latest version of Livebook and have fun! More of Launch Week 2 Day 1: Remote execution Smart cell Day 2: Speech-to-text with Whisper: timestamping, streaming, and parallelism, oh-my! Day 3: Introducing File Integration Day 5: Vim and Emacs key bindings releases launch week 7 months ago Introducing File Integration - Launch Week 2 - Day 3 Welcome to the 3rd day of Livebook Launch Week 2! ? Today, we’re excited to announce Livebook v0.11’s most prominent feature, file integration. Although file integration may not sound exciting at first glance, bear with us; we have some elegant features to show. Imagine code generation when you drag and drop a file based on the file type. Or quickly do a lazy reading of a multiple gigabyte parquet file stored in S3. That’s what we’re talking about! ? Watch the video where José Valim shows a demo of what this feature can do. Why? Throughout the last releases, we have been improving how Livebook helps to work with data. Data comes from different sources. One common source is a database, which Livebook already has good support for . Another source is a file, either on your machine or on S3, which Livebook hasn’t natively integrated with yet. Don’t get us wrong, you could already write some Elixir code in your notebook that reads a file from the file system or the web. But the Livebook UI had no understanding of it. And that’s what changed in this release. What’s the Livebook file integration? The concept is simple. When you’re editing a notebook, you can add a file to it. All files are listed in the sidebar, so everyone using your notebook can quickly glance at your file dependencies. Once you do that, Livebook exposes an API for your notebook to read that file via the Kino.FS module. But that’s not the only thing. Now that Livebook natively understands files, it can offer code suggestions based on the file type. For example, when you drag and drop a CSV file to Livebook, it can generate code that creates an Explorer Dataframe from that data: Or when you drag and drop a SQLite database file, Livebook can generate code that describes that database: Or when you drag and drop an audio file, Livebook can generate code that uses a Machine Learning model to generate a...