I’ve identified a number of core services that will need to be exposed to the rest of the platform. Many of these services could also be used outside the platform as well. Because of this, I’ve decided to write these services as WCF Binary Services. Utilizing this model will allow me to consume these services from the platform as well as any other client I create that may be able to use the functionality these services provide. It also gives me a lot of flexibility on how these services are hosted and implemented. For example, my guess is that these will be self-hosted services running with a Windows Service that I create. One of the benefits of this is that I can easily load-balance these services across multiple servers within my infrastructure. However, if speed becomes an issue, I can always just include these services directly in the client. Again, it’s about being flexible and saleable.
Here is a list of the services I will be working on first:
- File Identification Service – Identify the type of a given file
- File Hashing Service – Generating hashes and comparing hashes for individual files
- NIST Service – Identify files that are found in NIST
- Queue Manager Service – Add, remove and process task within the queue
No comments:
Post a Comment