Create a web API which services both client applications. Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP

I'd say that using those things does simplify scaling and deployment. It may be true for many things that you would benefit from that simplification while you could always "roll your own". Certainly for some though, you're not going to need more than a single container instance somewhere. For example, maybe you use containers so developers can easily pass around builds to host locally so that the code they are really focused on is able to hit those locally hosted containers as dependencies. Maybe especially beneficial if both sides of the fence are being worked. "A" depends on "B" but you are actively altering both. As you and others make changes, it isn't just the repos changing but the containers coming out of build pipelines reflective of those changes also. The most benefit is if those containers are artifacts that eventually hit testing/production environs. But that would/could still have benefit even if your "real environment instances" were hosted on cloud instances or even if they were not containerized. Provided you enforce that changes to the container must also be reflected in the environments they represent you still eliminate a bunch of "works on my machine". In simpler use cases, it might be that orchestration tooling complicates things more than simplifies them.

I am not @OriginalGriff.

That would be philosophy :). Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.

After some extra research I found a complete list of state from different sources: Running - The session is running one or more batches. When Multiple Active Result Sets (MARS) is enabled, a session can run multiple batches. For more information, see Using Multiple Active Result Sets (MARS). Background - The session is running a background task, such as deadlock detection. Rollback - The session has a transaction rollback in the process. Pending - The session is waiting for a worker thread to become available. Runnable - The session's task is in the runnable queue of a scheduler while waiting to get a time quantum. Spinloop - The session's task is waiting for a spinlock to become free. Suspended - The session is waiting for an event, such as I/O, to complete. Sleeping - A session in the sleeping state means a client connection without an active query. Dormant - SQL Server is resetting the session. Same as Sleeping, except Dormant also indicates that the SPID has been reset after completing an RPC event. (Replication SPIDs show "DORMANT" when waiting.) For more information about other columns see: SQL Server Activity Monitor I hope it helps others. SignatureNotFoundException

Sounds like Windows Home. Windows Pro doesn't do this.

Please have a look here: How do I fix the error 'Named Pipes Provider, error 40 - Could not open a connection to' SQL Server'? - Stack Overflow[^]

I confess I use SQL Server more these days than Oracle, but the only possible option I can find that would let you see multiple databases seems to be if you're using something like Enterprise Manager Cloud Control - [Extract the list of all databases with server and OS version of Oracle Enterprise Manager Cloud Control repository - My DBA World]([https://www.mydbaworld.com/extract-databases-server-os-version-of-oem-repository/\])

I'd rather let everyone that cares to look, how much I appreciate his help. Also, he can be presently suprised when he sees it. :-D

I used app.UseAuthentication and the problem solved.

Assuming you mean SQLite: Appropriate Uses For SQLite[^]: SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic. Note that writing to the database will lock the entire database file. Concurrent writes will not be supported. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

One thing I forgot to mention - if the rule is "no machine with direct internet access is allowed to connect to the database", then standard reverse proxy between the internet exposed endpoint and the "real" webserver will do the trick.

Have you seen Reggie lately? I wrote this Dismantling Reggie[^] which covers how Reggie works. The thing is, Norm works the same way, but instead of FA state machines for lexers and matchers, it writes PDA state machines for parsers. It's shockingly similar, so understanding how Reggie works will make understanding Norm par for the course. As far as understanding the process of generating the parse tables that the code is generated from, I've covered that in several previous articles and I won't be covering it that much when I cover Norm, any more than I covered the workings of the regular expression engine when covering Reggie. I'm just putting that out there FWIW, and so you know what to expect. Real programmers use butterflies

UTF-16 is the result of developers underestimating how many characters would be needed for a universal encoding and lingers like the stench of a soiled diaper because MS rushed it into production in the 90s before anyone realized it was a mistake. :doh: Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius

I *am* talking about the backend. This is a statement about infrastructure, not front end coding. If your DB is on a LAN, there's a good chance there's no DMZ which means a disgruntled employee could poison the database, probably pretty easily, unless there's security on the tables and validation. Real programmers use butterflies