Cloudflare tunnels are layer 7, so it’s not unlimited access by any means. This also means that certain things will break btw, for example if your website uses websockets to load information, that isn’t supported.
Next, I’d put the computer that is going to be hosting into an isolated vlan of its own and access via external URL only.
If you’re going to use docker images, make sure to vet that they’re updated often and always spin up the latest.
Sorry dude…writing simple queries is what I said was easy…and for the record they are. That example is probably not a great example. Simply from my experience, I never started my career in IT, I was in healthcare and far from it all.
Anyway, I’ve had some idiots approach me about their shitty ideas before too…most notably was one person asking to create an app that “uses AI” to help a person search for the right individual when they send a text message. Couldn’t explain how it would know that it found the right person? There was another one that wanted to track the origin of “content” and how it changes over time on social media… again “using AI”.
For my team I have a mirror that I set up and have a bunch of ELT jobs that load the deltas every night. Queries don’t ever run in PROD, if someone needs a specific view or more data, they go through me and my team. I also set timeouts, precisely to avoid the ahole from using Select * from. Also have a bunch of reports I created to see who is running what queries and timings. We review them quarterly or when someone complains or when a project that needs our data asks us for access.
We also have an autogenerated data dictionary for folks to use as well. Generally I don’t entertain any “it’s slow” complaints unless they go through the documentation, provide their exact query and write what it is they’re trying to get.
My assumption was that OPs shop does the bare minimum in terms of making sure they don’t shoot themselves in the foot.
Ooof my guy if you got folks running queries on your PROD db you got bigger problems even if they were the best SQL writers in the world.
You can’t fuck up step 1 and complain the rest of the steps aren’t working. I write and maintain a set of ELT jobs and a bunch of front end dashboards. By default, we never run analytics queries in PROD db. I create views and such for the simple queries to run.
I picked up SQL a few years ago for a school project. It took me a week. The DBA stuff just came by itself as I went along. Query optimizations took a while but you don’t need to write every query super optimally. If the DB tables are set up correctly your users will not have to worry about it at all.
My previous comment assumes you guys already have a db set up for analytics where folks can run queries. If you don’t then IDK how the director of IT got their job…That’s very basic shit.
SQL isn’t hard to learn unless they’re asking you guys to do T-SQL and PLSQL.
For simple queries it’s pretty easy.
Former healthcare to software engineer working on a master’s here. My colleagues who were licensed back in healthcare weren’t all of the same quality. They all made mistakes at one point or another, some pretty bad some minor. There’s no difference though, minor could just as well become major.
The way they get around it in healthcare is by throwing more people at the problem. You have a physician who is good at pointing in the general direction of the problem and a solution, then you have all the auxiliary staff who will narrow down on the solution based on their field. But at any single point all of them could fuck up, or one of them could.
Now that I’m a software engineer and I’ve written enough code to do stuff. I can confidently say that licensing will not solve this problem. Especially if there aren’t enough people involved. Which is probably what was missed in the beginning.
Anyway long rant over.
This sounds like an interesting project, what programming language did you use? Was the endpoint relative to the person making the query, how was the data stored?
This brings back some nightmares. Once I get them working I never upgrade or even look at them.
That document doesn’t say what layer. But it does say it supports Websockets.
Just odd that when I try to set it up using a named tunnel I don’t get an option to specify the WS service type. However it does require a service type if you want to connect to it.
Looking at this page it would seem that it’s a layer 7. Although I could be wrong, but my front end app has issues finding my backend service for websockets.
Granted I even tried to connect to my private computer using other protocols. I couldn’t get through. Anyway I’m most likely going to be taking that project offline soon.