SQLite is really easy to start using, you just need to add the library to your project and start issuing SQL statements.

Now, because it's so easy to start using SQLite, it might feel like it's configuration free, but that's not exactly true.

There are a few key configurations you should be familiar with, and in this video we'll look at one of the most important configuration options, the journal_mode option.

If you use a client/server based database (Postgres, MySQL etc) with tools like Object-Relational Mapper (ORM) or GraphQL, then your system is likely susceptible to the N+1 problem.

But did you know that not all databases are susceptible to the N+1 problem?

For example, SQLite doesn't experience the N+1 problem.

When you're at the beginning of a new software project, there's a question you should ask yourself, which is:

What architecture should you use for your application?
client/server or local or ...

Odds are, you probably don't explicitly ask this architecture question anymore, because you intuitively know the answer, which is almost always client/server right?

Compute needs are rapidly growing, and individual CPU speeds have not kept pace with that increase. The simple fact is they aren’t ever going to be able to - we face the everpresent constraint of the speed of light, regardless of how many transistors we can cram onto a chip. Sure, stacking CPU cores solves the raw processing needs, but just cobbling more cores into a single server can’t provide the redundancy for zero-downtime or the scale for massive computing jobs.

When we consider “the Edge,” it can be easy to forget that the edge is you. It’s your data. It’s your phone, your laptop, your wireless headphones, your smart tv, your browser tab.