Skip to main content

Determinism vs Nondeterminism

From P vs NP to system integration: why determinism matters, and how nondeterminism might already shape your business processes

Determinism or nondeterminism, two concepts that shape everything from science to philosophy. But what do they mean for system integration?

Sudoku, easy to verify, hard to solve.

Determinism vs Nondeterminism

The P vs NP problem

There is a classic and important problem in computer science called the “P versus NP problem.” As an aspiring developer and former math teacher, I was intrigued by the problem and specifically the terminology. First, let me try to explain the problem.

  • P stands for a problem that can be solved in a reasonable time by a computer (Polynomial time).

  • NP stands for a problem that can be verified in a reasonable time but not solved in a reasonable time (Nondeterministic Polynomial time).

For example, a sudoku puzzle can be verified quickly and deterministically. That is, if you want to check if a solution is correct, you can follow a given algorithm that will always take the same amount of time and will always give you the same answer (for the same puzzle).

To solve the puzzle, though, you must either use a nondeterministic approach and try different methods depending on your own hunches and feelings, or be prepared to spend a very, very long time trying to come up with a deterministic algorithm, that is identical for all sudokus, and then following it.

Why this matters

The question of the problem is whether P = NP. That is, if we can find a quick way to verify a solution to the problem, does that then mean that there is a quick way to solve the problem? The question is, as of now, unanswered, and if it were to be answered and found that P = NP, global chaos would likely follow.

“Imagine that hackers could find your password as quickly as they could verify that it was correct. Not good.”

Most modern cryptography relies on the fact that it is harder to find a solution than to verify it.

Another interesting aspect of the problem is that if you solve one special case of the problem (for example, the sudoku problem), you solve all cases of the problem. So if you are an agent of chaos, and, like the Joker of Batman, would like to see the world burn; make sure to spend some time on trying to solve this!

Clarifying Determinism vs Nondeterminism

  • Determinism: If the starting conditions are the same, the outcome will always be the same.

  • Nondeterminism: The possibility of different outcomes even though starting conditions remain the same.

In computer science the cause is often randomness; in other contexts the cause may be ascribed to free will.

From philosophy to system integration

Determinism vs. Nondeterminism is (and has been) a hot topic in fields ranging from physics to philosophy, but the reason I am bringing it up is actually the field of System Integration.

It seems like a no-brainer that integration flows should always be deterministic; that is, if you input A and get output B, you should always get output B when you input A.

Where Nondeterminism fits in system integration

Well, believe it or not, there is room for nondeterminism even in integration, where you generally expect predictable results.

How, you ask? Join us at our Agent in a Day workshop at Contica on October 22 at 16:00 on Masthamnsgatan 1, and we will try to convince you that this is the case.

You might even find out that your current business processes might be more nondeterministic than you think. And that getting more control over that nondeterminism is a good thing.

Footnote

The “P vs NP problem” is a complex and nuanced problem and I had to do some simplification to avoid being too verbose here. If you want to discuss the problem further or want to know more about the event, make sure to reach out!

Image description: Niels Bohr and Albert Einstein, two physicists with different views on determinism.

Reach out if you’d like to discuss determinism, nondeterminism or how AI can help you in your integration landscapeintegration challenges.

 

Dela detta inlägg


Post author image.

Författare: Håkan Åkerblom

AI Integration Specialist

Fler inlägg att sätta tänderna i

Jag skulle bara lappa ihop en prognos. Det slutade med att jag byggde den själv

Ania Lenestad är projektledare och har ingen teknisk bakgrund. När prognosen i Tempo inte räckte till byggde hon om Conticas kapacitetsplanering med Claude Code. Här berättar hon hur det gick till och vad som gjorde att hon vågade.

Från demo till produktion – när mötesanteckningsagenten kom ur malpåsen

I våras körde mötesanteckningsagenten fast. I oktober plockade Leonel Bylund fram den igen i Copilot Studio och upptäckte att det kluriga var allt runt omkring AI:n. Här är fyra lärdomar från vägen till en agent som går att lita på.

Agenter i Microsoft Foundry, och varför vårt arbetssätt blir mer vattenfall än agilt

Vad händer när det blir enkelt för vem som helst att bygga AI-agenter? Amanda Orrbeck tillbringade en dag på ALSO:s Agentic Hackathon med att skapa och deploya agenter i Microsoft Foundry. Hon gick därifrån med fler frågor än svar om hur integratörens arbete förändras.

Så kopplade vi ihop Teams, AI och Confluence för att sluta tappa möteskunskap

Mötesanteckningar hamnar någonstans, ofta i någons huvud. En projektledare på Contica byggde en AI-agent för mötesanteckningar som tar Teams-transkript, strukturerar innehållet och publicerar det direkt till Confluence med riktiga @-mentions på varje action item. Här är vad som fungerade, vad som inte gjorde det, och varför prompten visade sig viktigare än modellen.