Stripe VS PostgreSQL

First let's introduce the tool: Sorbet is a gem developed by Stripe that aims to bring type notation syntax and type checking support for the Ruby ecosystem by utilizing the "Gradual typing" philosophy, it also provide type generation from YARD comments via the tapioca gem, allowing to grow alongside the already built Ruby codebase.

For me Stripe is the peak for a product/company website:

https://stripe.com/

I heard some people admire https://linear.app/ but I don't see the appeal myself

Majority of websites often fall into one of two categories:

1. Traditional off the shelf template

2. Look cool but fail when it comes to usability and robustness (those featured on awwwards)

You could have the best service in the world, but if you have a payment gateway that leaves people feeling uncomfortable, you'll lose them. Not only that, but you have PCI compliance you would need to deal with and a slew of other things that are handled for you with a payment vendor like Stripe, Square, or PayPal.

First you'll want to go to Stripe's website and setup an account. Then install Stripe with pip install stripe. In this example I'm using Flask for the backend and React for the frontend. The website is an e-commerce page for buying and selling skateboards. Now create some models for the product to sell and the receipts then run flask db init, flask db migrate, and flask db upgrade to create the database. My models look like so:

I've spent my fair share of time in Silicon Valley on some of the coolest startups in the tech scene. So, a lot of our inspiration comes from companies like Stripe (e.g. their landing page) and Linear (e.g. their gradient usage). And, the data display architecture you're referencing (down to the layout on shift on screen sizes) is almost a perfect clone of the NBA's. And there's definitely a team there that costs 7 figures who has researched every nook and cranny about making that the most optimal layout haha.

Look, absolutely millions of people are going to type credit card numbers into https://amazon.com and https://stripe.com and https://squareup.com/ this year and nobody will get their credentials stolen or their credit card compromised. I mean, far far fewer then from the waiter or checkout person taking a quick photo of your credit card while they run it through the Point of Sale device physically.

Toast uses SSL. So does Stripe (https://stripe.com/) and so does Square (https://squareup.com/us/en/payments). Everybody, without fail now uses HTTPS (SSL), they really do. That ship sailed. If you use the Chrome web browser, anything not serving up puppy pictures over HTTPS says "Not Secure" for the last HALF DECADE. If you google "PCI compliance" it's literally THE LAW that it is required for handling credit cards. Anybody not using HTTPS will get fined, and probably go to jail. The embarrassment of the programmers getting caught not using HTTPS would be amazing, like they would have trouble ever getting another job programming computers.

Stripe

I was developing a backend that integrates Stripe to manage customers and to process subscriptions. In one use case, it should search for user input in the metadata of Stripe subscriptions. When I looked up the documentation about how to use the search functionality I came across the Search Query Language. It looked like users could easily inject their own additional query clauses. After a simple check: Yes, e.g. for the user input "124' OR status:'active" all active subscriptions are returned as well.

Stripe is a complete payments platform that offer a developer-friendly way to accept payments online and in mobile apps. To learn more about Stripe, visit their website here.

SQL (Structured Query Language) databases are relational databases. They organize data into tables with rows and columns, and they use SQL for querying and managing data. Examples include MySQL, PostgreSQL, and SQLite.

Node.js, MySQL and PostgreSQL servers installed on your machine

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

I've used MySQL for years. But recently, I found myself working PostgreSQL and simple things like dumping and restoring a database are different enough that I decided to document the process. It's straightforward enough once I knew how.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

PostgreSQL

PostgreSQL: Offers a robust feature set and strong compliance with SQL standards, making it suitable for a wide range of applications, from simple to complex, particularly where data integrity and extensibility are key.

FerretDB is an open source document database that adds MongoDB compatibility to other database backends, such as Postgres and SQLite. By using FerretDB, developers can access familiar MongoDB features and tools using the same syntax and commands for many of their use cases.

To better understand how SQL injection works, let's quickly create a vulnerable app using Node.js, Express, and a PostgreSQL database. The application takes user input from a form, constructs a SQL query, and executes it against the database to fetch some data.

We'll use PostgreSQL, and first of all, you need to install PostgreSQL if you haven't installed it yet. https://www.postgresql.org/