To fully leverage the data is the new oil concept, companies require a special database designed to manage vast amounts of data instantly. This need has led to different database forms, including NoSQL databases, vector databases, time-series databases, graph databases, in-memory databases, and in-memory data grids. Recent years have seen the rise of cloud-based streaming databases such as RisingWave, Materialize,... - Source: dev.to / 4 months ago

Some recent solutions to this problem include Differential Dataflow and Materialize. It would be neat if postgres adopted something similar for live-updating materialized views. https://github.com/timelydataflow/differential-dataflow. - Source: Hacker News / 8 months ago

Materialize | Full-Time | NYC Office or Remote | https://materialize.com Materialize is an Operational Data Warehouse: A cloud data warehouse with streaming internals, built for work that needs action on what’s happening right now. Keep the familiar SQL, keep the proven architecture of cloud warehouses but swap the decades-old batch computation model for an efficient incremental engine to get complex queries that... - Source: Hacker News / 9 months ago

Materialize | EM (Compute), Senior PM | New York, New York | https://materialize.com/ You shouldn't have to throw away the database to build with fast-changing data. Keep the familiar SQL, keep the proven architecture of cloud warehouses, but swap the decades-old batch computation model for an efficient incremental engine to get complex queries that are always up-to-date. That is Materialize, the only true SQL... - Source: Hacker News / about 1 year ago

Materialize | NY, NY | https://materialize.com/ The Cloud Database for Fast-Changing Data. We put a streaming engine in a database, so your team can build real-time data products without the cost, complexity, and development time of stream processing. Cloud team openings: https://grnh.se/0ad6ab6b4us Senior PM openings: https://grnh.se/415c267f4us. - Source: Hacker News / about 1 year ago

Let me be blunt: I dislike (hate?) Go for its error handling approach. However, with close to zero knowledge of the language, I was able to build a basic HTTP API that reads from the database in a couple of hours. I chose Gin Gonic for the web library and Gorm for the ORM. OpenTelemetry provides an integration with a couple of libraries, including Gin and Gorm. On the Dockerfile side, it's also pretty... - Source: dev.to / 20 days ago

Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs. A lot of them also have conventions for the frontend, where the assets usually are stored in /public, so they can be go:embed later as an embed.FS instance into the binary. Having said that, there's plenty of examples on github. I'd recommend to take a look at bigger projects or templates and understand how... - Source: Hacker News / 5 months ago

Excellent Performance: Sponge is built on the gin framework, providing outstanding performance for web service development. - Source: dev.to / 5 months ago

In this blog, we will delve into the fascinating realm of handling images in a Golang application, leveraging the power of the Gin framework for RESTful API development, MongoDB as a robust NoSQL database, and the mongo-driver library for seamless interaction with MongoDB. To store images efficiently, we'll explore the intricacies of GridFS, a specification within MongoDB for storing large files as separate chunks. - Source: dev.to / 5 months ago

For building the RESTful Point of Sale service API, I've considered and selected a combination of technologies that would work seamlessly together. For handling HTTP requests and responses, using the Gin HTTP web framework would make sense because I think it seems complete and popular among Go community too. To ensure data integrity and persistence, I'm using PostgreSQL database with pgx as the database driver,... - Source: dev.to / 9 months ago