- Yes, using Microsoft SQL Server for Linux; hosted both on-premises with VMware and in Azure Virtual Machines - later migrated to Azure SQL Managed Instances. It worked great for the business’ needs. The major architectural advantage was that each Customer had a completely isolated Tablespace, easing compliance auditing. Each DB could be exported/migrated to a different Instance or Region, and migration scripts running slow for “whale” customers had no effect upon small fish. Monitoring of the Servers and individual Instances was straightforward, albeit very verbose due to the eventual Scale.
There were a few administrative drawbacks; largely because the MS-SQL Server Management Studio tools do not scale well to hundreds of active connections from a single workstation, worked-around through lots of Azure Functions runs instead. Costs and instance sizing were a constant struggle; though other engines like Postgres or even SQLite would likely be more efficient.
I have also seen this used in other formats quite successfully - Fandom/Wikia (used to?) use a MySQL database for each sub-site.
Have been working across technical disciplines since the 1990s, always looking for Interesting Problems to solve. Please let me know if you have any questions about my background - I can guarantee an interesting story!Location: United States, New York Metropolitan area Remote: Sure Willing to relocate: Within continental US Technologies: Web, Networking protocols especially DNS, Virtualization and Clustering, Databases of all types from CSV and SQLite to CouchDB and MS-SQL, Revision Control/CI/CD (git and friends), distributed filesystems, many Languages Résumé/CV: https://kashpureff.org/eugene/resume.html Email: In Resume- Computing Power has increased tremendously, along with the higher resolution of digital imaging technology compared to analog film plates. Sky Survey projects like the Vera C. Rubin Observatory have become active in recent years, which generate Terabytes of spectrographic data each night which can be rapidly examined for differences from previous captures. In the past each exposure had to be hand-aligned on a Light table and “flipped” between to spot differences.
- Location: Northeastern United States
Remote: Maybe
Relocate: Yes!
Technology is constantly evolving. Most recently familiar with the PowerShell/C#.NET ecosystem, but not exactly looking to reprise that experience. Worked primarily with Interpreted languages ranging from Perl, PHP since version 3.1, Brainfuck, Python, Ruby, Lua, various flavors of Shell, and many more. Not scared of Compiled Languages or Assembly.
Email: Eugene@Kashpureff.org
Employment History: Upon Request. Most recently at Microsoft - departed for Family Reasons.
I am seeking a Position which is Technically Interesting. I would like to be part of a Team working towards a common goal that improves Society, rather than a collection of Individuals connected only by their Salaries at a megacorporation. I am not searching for any specific Job Title - you may be looking for a Software Engineer, Business Analyst, Technical Manager, Security Researcher, Systems Architect, or maybe just a part-time Consultant. In my career since 1995 I have chased bizarre memory-alignment performance regressions in C code for a Physics library, built distributed database replication systems with leader-election consensus, chased timing issues within Multiplayer game protocols, implemented Financial audit controls to identify untrustworthy employee behaviour, built Monitoring & Active DevOps response systems for “Five-ish Nines” Uptimes of customer Environments, designed and installed redundant Low-Voltage and High-Voltage Electrical systems on Ships (DP2 standards) and in Data Centers, performed physical security penetration testing for Restricted Sites, and participated in a takeover of the Global Domain Name System’s root servers.
If you have any Questions, please send me an Email!
- The NEXRAD weather radar system has multiple modes of operation (Volumetric Coverage Patterns) configurable for each antenna site. Each of these is optimized for different weather conditions. The light-blue returns represent humidity in the air (not quite rain or fog) and is usually tuned below the “noise floor”.
Current operating modes: https://www.roc.noaa.gov/branches/operations-branch/current-...
- A few months earlier there was only a single “Enterprise 6000” cabinet: https://kashpureff.org/album/1999/1999-05-30/M0000024.jpg
- I was just the Teenage intern responsible for doing the PDU Cabling every time a new rack was added, since nobody on the Network or Software Engineering teams could fit into the crawl spaces without disassembling the entire raised-floor.
I do know that scale-out and scale-up were used for different parts of the stack. The web services were all handled by standard x86 machines running Linux - and were all netbooted in some early orchestration magic, until the day the netboot server died. I think the rationale for the large Sun systems was the amount of Memory that they could hold - so the user name and spammer databases could be held in-memory on each front end, allowing for a quick ACCEPT or DENY on each incoming message - before saving it out to a mailbox via NFS.
- Throughout the late 90s, “Mail.com” provided white-label SMTP services for a lot of businesses, and was one of the early major “free email” providers. Each Free user had a storage limit of something like 10MB, which is plenty in an era before HTML email and attachments were commonplace. There were racks upon racks of SCSI disks from various vendors for the backend - but the front end was all standard Sendmail, running on Solaris servers.
Anyway, here’s the front end SMTP servers in 1999, then in-service at 25 Broadway, NYC. I am not sure exactly which model these were, but they were BIG Iron! https://kashpureff.org/album/1999/1999-08-07/M0000002.jpg
Presumably, testing how many readers believe this contrived situation. It was never a real Engineering exercise.