It is easy to mock when you don't even know that databases can and do and should process data, and they also do have their own battle-tested abstraction mechanisms.

How to use PostgreSQL directly from frontend, learn here:
https://lnkd.in/d8vE8pnV

p.s. I added the comment and reactions section so you can tell me how is this a stupid idea.

Vedran B.

The fastest micro-ORM for .NET: Norm is the high-performance micro-ORM modern Dapper replacement for .NET Standard 2.1 and higher.

Check it out here:
https://github.com/vb-consulting/Norm.net

Svelte .NET Razor Template
https://github.com/vb-consulting/RazorSvelte

PgRoutiner - Database-First Development with PostgreSQL and .NET:
https://github.com/vb-consulting/PgRoutiner

NpgsqlRest Automatic PostgreSQL Web Server

Let me show you something. This is from the real production system. I might get myself in trouble for doing this, but, nah, I don't think so. More like chewed out. I've been chewed out before.

This chart shows resource consumption on the application server that is running a periodic background job that:

- Pulls some data from the database
- Does some calculations based on the business logic
- Saves the data back to the database

And after rewriting everything to run that business logic INSIDE the database, using modern SQL with lateral subqueries, window functions, aggregates, etc, everything, all nine yards ....

- Application server resource consumption is now flat.
- Database server, that now does all the work, doesn't even register a bump in resource consumption. I mean, it is there, somewhere. I can see that the data shows that calculations and "muh business logic" is just fine, but resource consumption doesn't show any change. I mean, I have to zoom really hard to even notice.

So, yes, now ask yourself how much that stupid mantra that we've been listening to for the last 20 years - "business logic doesn't belong to the database" is worth to you.

And put this into calculation before you start preaching Clean Hexagonal DDD or whatever that commands "no business logic in muh database".

Have a nice day.

The cleanest architecture has PostgreSQL at its core. Important Dependency Rule: everything points to PostgreSQL.

P.S. Uncle Bob approves this architecture.

I'm trying to write a new blog post that will be 100% humanly written (by me) and it is surpassingly hard.

Close the Claude Code, turn it off. Claude Code you shut up now. Fine.

Starts typing, write first two words, Copilot adds entire two new paragraphs. Shut up you Copilot you, no one asked you a damn thing. How do I turn this thing off? Ask Claude Code, turn it on again. He sees me writing a new blog post, damn it, who told you, is that Copilot again?

Alright, alright, but at least I have to give it to Grammarly to check my Balkan english. Does that count as AI assisted now? Im so confused. It feels like Im caught in AI web now, no way out AI world now, that's it.

I just want to tell the story in my own voice, you know. I even created a custom badge for this post, look:

Many such cases. 

OOP pushed by DDD has become a dog chasing it's own tail.

I've been seeing more and more posts on tech Reddit like that.

Good. Push back against lunacy.

Vedran Bilopavlović

Here is a really, really interesting side-by-side comparison I did with a little help from AI. You tell me, is it far off from reality?

1. PostgreSQL analytical query

Fairly complex zero-islands detection analytical query in a hypothetical IOT scenario. Something that you would probably have to write ad-hoc if some of your devices malfunctions. It detects consecutive zeros in data, and it runs very fast.

2. Same query on MongoDB

I'm not sure how this would even run, but AI says not too good. Query planners are not even comparable. If we ignore the sheer ugliness of that query (if you can even call it that), and let's just say that it is a matter of personal taste (although the Mongo version is longer), why would you want to deprive your system of these kinds of ad-hoc analytics?

But wait, it gets worse. Let's say, we don't want this to be ad-hoc anymore - we want this to be on our dashboard.

3. Same PostgreSQL version in modern C# and .NET with EF and modern DDD

As we can see, modern EF has limited support for window functions. You can do one window function (and with a limited subset) via an extension that would translate a grouping expression into a window function (which makes it even more confusing, is it a grouping or a window function), but it cannot do two consecutive window functions one after another, so we must fall back to raw SQL.

But wait, it gets worse.

4. Modern C#/.NET fully Linq/DDD and everything

But we can always listen to wise advice from our beloved gurus and keep this business logic out of the database and SQL out of our codebase.

Nevermind that our codebase has now doubled again and bloated out of proportion (we haven't even got to the unit tests, oh boy), we are now actually downloading the database into memory in order to be able to process it properly. Performances of something like this are going to be abysmal.

And yet, so many teams are prepared to do exactly this - they are making their users suffer and wait for responses and pay huge cloud bills, just to make their domain pure and clean.

Insanity.

But, wait, it gets worse.

5. MongoDB with modern C# and .NET and DDD

At this point, I don't know what to tell you anymore. Just learn SQL. Thank me later.

PostgreSQL IS your application layer. Period. It is the center of the system. All dependencies point to PostgreSQL.

Write your business logic there. You have many options to write PostgreSQL code and myriad if languages to choose from.

Yes, yes, I know it is contrarian heresy in 2025. Maybe you got burned once in the early 2000s working on some monolithic Oracle nightmare. Fair. But this is something else entirely.

I also completely understand, it's not mainstream to do so, and if you don't do what is mainstream, what will people think of me. Trust me, I know.

But honestly, are you satisfied with mainstream? Do you enjoy mapping data between those layers. Doing OOP still with your database, eh, how that works out for you? How responsive your application really is? What is your development velocity?

What if I told you that you can do everything declaratively, just declare WHAT you want, don't even bother with technical details. Everything with 70-80 percent less code with performances those mainstream apps can only dream.

Well, NpgsqlRest processed 280k requests in 60 seconds. PostgREST processed 60k. Same PostgreSQL function.

Just put PostgreSQL in central and let those declarations (yes, declarations, don't worry abou tech details) - handle everything else:

- End-to-end safety, sny way you want, you got it.

- End-to-end type checking, you got it.

- Server Sent Events, Uploads, Ingestion, Caching, Retries, Proxies, Rate Limiting, Load balancing, you name it, we got you covered with few simple declarations.

System is completely declarive to a point that even AI doesn't have to be trained, they already understand the human language.

All you have to do is to do declare your business logic. What is it that you want. In PostgreSQL.

Read more here:
https://lnkd.in/dgFCCFEm

Not every endpoint requires a database connection. 

When you don't need anything from the database, you simply declare a reverse proxy endpoint with an empty function that does nothing, and still have all other features declared in annotations (security, caching, rate limiters, etc), and still client TS/JS code auto-generated from a function signature.

This article explains an advanced NpgsqlRest example that involves a reverse proxy endpoint written with Bun that acts like an AI mock service. 

So, no, there are no limits to what NpgsqlRest can do.

https://lnkd.in/dR5Urapu

I don't have anything smart to say about AI. The worlds best and brightest minds are on the case. But I do about PostgreSQL. What else to do on hangover Sunday, and I'm right?

Did you know you can format PostgreSQL intervals to a human-readable format directly in PostgreSQL?

Well, neither have I.

If we go and create an interval:  "select 8197156465 * interval '1 ms'" It returns boring "2276:59:16.465". Not very nice.

We can use the function "justify_interval" that adds days and months if the interval exceeds 24 hours, and so this "select justify_interval(8197156465 * interval '1 ms')" returns this: "3 mons 4 days 20:59:16.465". A little bit better, but we can do even better than this.

There is a setting called "intervalstyle" which is by default set to "sql_standard". We can set it to "postgres_verbose".

However, doing "set intervalstyle = 'postgres_verbose';" would affect the entire connection (session), which is problematic if we use a connection pooler (and who doesn't). So we must set it locally to a transaction scope, and in order to do that, our query needs to run in a dedicated transaction. So now we can do this and try with and without "justify_interval" function:

begin;
set local intervalstyle = 'postgres_verbose';
select 
    8197156465 * interval '1 ms',
    justify_interval(8197156465 * interval '1 ms');
rollback;

This returns two columns:
@ 2276 hours 59 mins 16.465 secs	
@ 3 mons 4 days 20 hours 59 mins 16.465 secs

For some reason, this PostgreSQL interval includes "@ " in front of every interval. So we can trim that:

begin;
set local intervalstyle = 'postgres_verbose';
select ltrim(justify_interval(8197156465 * interval '1 ms')::text, '@ ');
rollback;

Yields "3 mons 4 days 20 hours 59 mins 16.465 secs". Much better than "2276:59:16.465".

Just don't forget to read from the 3rd command (instead of the 1st), and that is it.

This Bun thingy is getting crazier and crazier but in a good way. 30% faster, 50% faster, etc 

I'm using it for a frontend build scripts and occasionally for some server services when needed for simple tasks, but more and more.

Crazy how we all got used of living woth JavaScript and all it's quirks and logical black holes.

Can't beat them, join them.

https://lnkd.in/d2zcYh5C

I am actually thinking of buying a pizza and coca cola to Claude Code to show my gratitude. Like every responsible and good manager does. Am I right.

Scrolling trough tech interwebs is new doom scrolling but only for software development:

- Software Engineering is just about to die
- Software Engineering is not dead yet, it just smells real bad
- Software Engineering is dying
- Software Engineering is almost dead
- Software Engineering is dying and is dead
- Software Engineering is buried

You mean to tell me no more ORMs, no more DTO mappings, no more DI configurations, no more Repository Service Unit of Work Query Builder Domain Object Immutable Record bullshit? Is that what you saying? Good riddance.

And why we were doing that in the first place? 

Just to execute the query on something like PostgreSQL that looks something like in this picture bellow?

If software engineering is dead, and AI generates all the code, then we certainly can skip all of that and just instruct AI to construct raw SQL — and cover everything with AI-generated tests.

Think about it:

☑️ Schema is the full context, everything that AI needs actually a single source of truth
☑️ SQL is the best-understood language, LLMs have seen more SQL than any framework in existence.
☑️ One artifact per feature, no coordinating across layers, fewer hallucinations
☑️ Instant verification — test the function with Pg/PlSql asserts, not through 7 layers of abstraction

That is, if you use automatic web server you your PostgreSQL: https://lnkd.in/dVsE-3Q8

☑️ Less context means fewer hallucinations, AI can't mess up your DI config, domain whatever or immutable thingy if there is none 
☑️ If so much code is either automated (http, endpoints, infrastructure, etc) or auto-generated (TypeScript fetch modules, HTTP files for testing, etc) - then we have reduced our chances for bugs and errors.

It is a radical concept, but such are these challenging times. I believe this is the way.

Hi everyone,

there has been an exciting new features added to NpgsqlRest lately, and I wanted to personally write a blogpost to describe what I have done.

So this will be completely human-written and complete with human-witten badge. I did used some AI for research but I haven't done much of grammar checking.

Anyway, now you can do nested JSONs with complex structure and even JSON with so called Multisets, arrays of objects containing arrays of objects and so on. 

All from SQL. All with generated clients, including you beloved Typescript with type safety out of database enabled.

I also described drawbacks and limitations and even workaround.

Check it out here and tell me what you think. 

- Is this abuse of the PostgreSQL type system?
- Does this violates everything we know about best practices?
- Another contrarian heresy?
- Revolutionary breakthrough?
- Uncle Bob would upset if he finds out?

Im curious...

https://lnkd.in/d5325hYs

I don't understand modern frontend any more. What the hell is this now. Just render my page for the love of God!

https://lnkd.in/dcNZAk6A

Oh, but there is, and very much so.

I respect Lucas Eder very much, especially for his talks on SQL that's some next-level red pill stuff, but he is just trying to sell his ORM here.

According to Wikipedia defintion, the object–relational impedance mismatch is a set of difficulties going between data in relational data stores and data in domain-driven object models.

He says that are absolutely no conceptual difference between these two:

SQL
CREATE TABLE author (
  first_name VARCHAR(50),
  last_name VARCHAR(50)
);

Java
class Author {
  String firstName;
  String lastName;
}

Oh, but there is. 

One concept lives exclusively in memory and requires a memory structure (list, collection, array, whatever) - and the other has abstracted memory and storage and is limited only by storage size.

That's quite a big difference, wouldn't you say? 

The only way to erase conceptual differences between those two and eliminate object–relational impedance mismatch completely is to have your ORM implement relational database features. And why would you want to do that when you already have, well, a database?

But, alas, there is a better way. Just use PostgreSQL and skip the middleman completely. I call it PostgreSQL Driven Development or PostgreSQL first or Clean PostgreSQL, I haven't yet decided on the name. 

Check it out here:
https://lnkd.in/dh6EHbsq


https://lnkd.in/dRpZUgvc

NpgsqlRest vs PostgREST vs Supabase

It's not even a competition at thus point... it was actually a side quest for NpgsqlRest. Supabase and PostgREST are fighting the loading screen.


https://lnkd.in/gcSSSRuH

Why is NpgsqlRest different from anything else out there?

Here is short summary of enterprise-grade features for production APIs... I mean besides declarative HTTP calls, live notification with server-sent events, auto generated clients from metadata, and bunch of other things...

Read more about it here: https://lnkd.in/dkgm8W-T

I wanted to do review of this article this morning but I realized it was AI generated story, tell-tell signs are all over. It might not be even real.

But I really was in such situation when newly appointmentee CV driven team leader went all crazy on microservices and I left (and not just me).

I often wonder what happened with bug brain genius move. Oh well, I will probably never know and ulit doesn't even matter.

It's okey when people use AI tools to help rhem craft a story. I just think that we should be much more honest about it.

https://lnkd.in/dgD-Zs4E

NpgsqlRest also supports automatic CRUD API generation over tables and views for following operations:

- Select, 
- Insert, Insert Returning, 
- Update, Update Returning
- Delete, Delete Returning
- On Conflict Do Nothing  for Update, Delete, and Insert statements with or without Returning operations
- On Conflict Do Update for Update, Delete, and Insert statements with or without Returning operations

This is might be good for extremely rapid prototyping and zero to hero scenarios for people not trained with SQL.

However, User-Defined Functions (or Stored Procedures) approach (described here: https://lnkd.in/daRHFfuP) is by far superior, especially in combination with scripted testing and AI tools.

https://lnkd.in/dUMSgZCv

taplio

Vedran B.'s Linkedin Analytics

Vedran B.

Performance ScoreVedran B.'s LinkedIn Performance

What is Vedran talking about?

Vedran B.'s Best Posts (last 30 days)

Ready to grow your LinkedIn presence?

taplio

.css-6ytdur{background-image:linear-gradient(284deg, rgba(39, 43, 72, 1) 0%, rgba(33, 47, 183, 1) 100%);color:transparent;-webkit-background-clip:text;background-clip:text;}Vedran B.'s Linkedin Analytics

Vedran B.

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Vedran B.'s LinkedIn Performance

What is Vedran talking about?

Vedran B.'s Best Posts .css-1emoo84{font-size:var(--chakra-fontSizes-md);font-weight:400;color:var(--chakra-colors-gray-600);}(last 30 days)

Ready to grow your LinkedIn presence?

Vedran B.'s Linkedin Analytics

Performance ScoreVedran B.'s LinkedIn Performance

Vedran B.'s Best Posts (last 30 days)