Please spell PostgreSQL correctly in the README

[kdekooter]

It hurts when the name of the world's most awesomest database is mangled like this.

[tobyhinloopen]

#4

Happy?

[kdekooter]

Nice! Approved them twice :-).

[rkops-bd]

We discontinued the support for PostgreSQL. The docker image is configured with MSSQL.

[kdekooter]

So much for open-source...

[tobyhinloopen]

I'm just happy the app(s) are on Github! A great step towards better software for our country. I hope this becomes the new standard.

[kdekooter]

Sure, that is a great thing. I just don't understand why any dev would pick SQL Server when Postgres is a option. Would save them a lot of future headaches!

[tobyhinloopen]

I never had any headaches with using SQL Server, PostgreSQL, MySQL or SQLite. They're all just fine. Just use whatever you're most experienced with, I suppose.

I suppose SQL Server plays nicely with C#/.NET?

I would use PostgreSQL as well, because I'm most experienced with PostgreSQL. but I would also not use C#, since I'm more experienced with other tools. The best tool is almost always one you're most familiar with.

[kdekooter]

DX issues aside, as a citizen I don't feel comfortable knowing that my data might end up in a proprietary database.

[tobyhinloopen]

Where does that stop? Do you want to drop C#/.NET too? What about the server it's running in? I suppose you also don't want it to be using a proprietary OS, so that leaves Linux (but who's using that, right?) with only open-source drivers.

Next the software needs to run on some kind of hardware. You can't use a proprietary cloud, so let's put a server in a rack somewhere. Oh, Intel and AMD server CPUs aren't open source either. God knows what these CPUs might be doing in the background!

So to make the whole stack open source, we first have to design our own hardware. Also, how can we be sure the open source version we've access to is the same thing the software is running on?

[kdekooter]

I had high hopes for all of this stuff to be open and transparent. But step by step things appear not to be so open...

[bwbroersma]

We discontinued the support for PostgreSQL. The docker image is configured with MSSQL.

@rkops-bd Can you elaborate on this decision? Maybe if you share the issues, the community can either better understand, or help with a solution.

[jellelicht]

@rkops-bd any chance you could elaborate a bit on why y'all decided to move database implementations in the end?

[dirkx]

@jellelicht @bwbroersma As we get closer to production the focus changes.

For this we're relying on the 247x ops of the Belasting dienst, existing dual DC environment, Security Operations Centres, monitoring, backups, etc, etc.

In that environment it is MS SQL Server that is the norm. And our timelines/priorities dictate that we go as fast as we can; so re-training and retooling 24x7 staff in PostgreSQL, getting that monitored, etc, is simply too much risk.

Which means SQL Server. And only that.

So while PostgresSQL served us well during dev, field and test - it is no longer important as we go life.

However - we'll try to accept patches if people want to keep things compatible. But for now - getting in production & dealing with Covid is our priority.

(@dirkx - die zelfs IIS boven apache prefereert als het ons sneller in prod krijgt).

[jellelicht]

If "speed" was the major concern, you would've found a way to do more work out in the open 😉 . That predictable speed + legal compliance outweigh some perceived purity/ideological shenanigans is completely understandable though. Thank you for your explanation @dirkx , it would have been nice to have something of the sorts shared at the same time as the decision.

[marekq]

So you now need Windows Server and MSSQL licenses to deploy this - because it's easier for a few select individuals. We end up with a static, old school infrastructure that requires expensive commercial licenses and isn't easy to port to OSS.

[jellelicht]

BD is no longer in the picture as far as I understand it, so please reconsider this decision, or explain why it would still be the most strategic choice to stick with MSSQL for now.