If you represent an end-user firm and would like to start with a free Observer Membership, which entitles you to attend key STAC events and access one item of non-public information from the STAC Vault, please respond via the online form.
STAC-E3 defines benchmark specifications for order management systems (OMS). Workloads involve receiving orders, cancels, etc. from "Initiators" and acknowledgements, fills, rejects, etc. from "Responders." Tests will measure latency, throughput, and resource efficiency while varying the input and output requirements.
STAC provides product development organizations with help across all four C's of competitive strategy by enabling a better understanding of what customers want, what competitors offer, what collaborators (partners) can bring to the table, and how the company's offerings stack up.
If you're responsible for marketing or selling high-technology products into financial services, you're looking for ways to reach prospective customers who are truly interested in your products and are able to influence purchase decisions. And you want to cut through the hype and FUD with clear, unshakable messages about your products' capabilities. STAC can help.
Engineers build and maintain the systems that the world depends on, from applications and middleware to systems, networks, and storage. The engineers behind today's financial infrastructure are under pressure to improve performance and reduce costs even as they introduce new functionality. With so much riding on their shoulders, engineers need the best information and tools they can get their hands on. STAC helps in a number of ways.
CTOs, architects, and heads of technology in financial firms have a tough job today. One the one hand, they are expected to provide technology leadership that will position their firms well for the future. But they're asked to do this in an environment that is buffeted by consolidation, cut-backs, and constant change. Taking the wrong technology path has bigger consequences than ever before.
In performance-sensitive businesses, application development is largely about managing tradeoffs. Those tradeoffs could be throughput versus latency, speed versus accuracy, or some other aspect of performance versus other application behavior. But they could just as easily be tradeoffs between application performance and developer productivity. Engineering for today's highly parallel environments is non-trivial, to put it mildly.
STAC provides resources that help developers understand those tradeoffs: