DS Plugin System
System is based on TDataModule structure and provides you with flexible way to manage your plug-ins. You can create them as a BPL or DLL; you could mix them in your application.
System provides you with Delphi IDE wizard to help you create initial code for your Plug-in, after this you could extend functionality in any ways.
Structure of the system allows you create independent as well as dependant plug-ins. In second case you could specify plug-in dependency, which means plug-in itself will control environment it runs in and inform you (plug-in manager) when required information is missed. This could help you handle many situations when system became unstable because some components of system not available as well as allow you handle intermodular dependency during load process.
One more advantage of the system is its real time configuration - you can register and unregister or load and unload plug-ins at any time. System supports thread-safe mechanism and provides you with lock/unlock functionality.
DS DB Anywhere
These days many Software companies develop database applications which require having a Database Access. This means providing support for Database Servers.
It is become to be not so important what kind of Database servers you work with. It could be a Microsoft SQL Server or Oracle, Interbase or MySQL, but no matter what you have to distribute their Database Structure between different sites/locations. It will be no problem if Database structure was static, but it is almost impossible today.
Many application life is Customer driven, which lead us into situation when every day, week, month or even a year you need to upgrade your customer database structure to be up to date.
Usually Database Systems you are using provide you with a tool which will allow you distribute your changes. But a common limitation will be what you will be "linked" to this tool and be able using only functionality this tools (Database Server) provides.
Most likely it will be something what will allow you upgrade a database between two sequential versions... You will not be able track easily changes between a versions or upgrade a databases with a gap in versions.
What you will have instead is a set of files (scripts) which describes changes of your structure between each version and to be able upgrade customer systems you have by running those scripts one by one.
This will cost you upgrade time and lead you to possible errors when you could miss some changes between versions.
We have a solution for this - DS DB Anywhere.