I've been tasked with looking if a combination of NoSQL (in this case possibly Neo4J) and
SQL-Server is a possible solution for a performance problem we've been having.
Part of my technical analysis is the maintainability and stability of the platform.
And this means I need to find a way to properly document, and maintain applications (the NoSQL) that are seldom used, in combination with an application we have specific and strict guidelines for (the SQL-Server).
My concern is mainly that when I review similar setups done in the past, one-shot applications tend to fall into black box situations, despite having originally been created in-house.
Those that aren't
black boxes tend to fall on the shoulders of a single, unfortunate person who ends up spending most of his working day maintaining and handling some
access database antiquated technology that nobody wants to touch and is apparently mission critical.
How do you, as the lucky sysadmin that is tasked with the setup and documentation of this platform make sure that your
monstrosity awesome setup stands the test of time?
How do people generally handle one-shot smaller applications in larger corporations, hopefully without permanently shackling their own name to the application?