rajatjain / stroika Goto Github PK

Stroika is a C++ application framework designed to make high performance, modern, reliable and threaded applications easier to write.

• Nearly all public interfaces and methods are well documented; implementations are clear and well commented.
• An elaborate system of built-in assertions (including thread-safety assertions) helps document and enforce usage patterns (without performance cost in production builds).
• Each release is tested with Valgrind, Google Sanitizers, and a variety of platforms and compilers, as well as a large body of regression tests (including most documentation examples) to help assure library correctness.
• Sample applications help show common use cases (like building a web server into your app to deliver web-service content and APIs). Quick start using pre-built Docker containers.

• Container classes (Collection, Queue, Mapping, Sequence, Set, and much more with rich variety of backend implementations).
• DataExchange (VariantValue, rich collection of data format serializer/deserializers - like JSON, object to/from serialization mappings, and much more).
• Execution pattern classes (external process runner, synchronization patterns, blockingqueue, threadpools, and much more).
• Networking support (high level socket wrappers, Web client fetching).
• Simple, elegant streams library, with adapters for cryptography, compression, text transforms, etc.
• Seamless integration with many important libraries, including: boost, libcurl, lzma sdk, openssl, sqlite, xerces, zlib (e.g. wrap a compression stream - using for example zlib).
• Framework libraries for network measurement, SSDP/UPnP, system performance monitoring, text editing/word processor, web server, web services, and much more.
• and much more...

• Stroika's biggest strength is also its biggest weakness:
  • There are smaller, more focused libraries that do many of the things Stroika does. Being single purpose is a form of modularity (good) and allows for easy adoption/integration. But libraries that do anything of any complexity must create their own infrastructure for a wide variety of building block problems (e.g. Xerces has its own stream classes, pistache date classes, etc). And if you have two such libraries, they are unlikely to interact seemlessly, and their support classes (for stuff like date and streams above) certainly won't.
  • Stroika takes the approach of building its functionality in layers, leveraging other components (e.g. Streams and Containers) in lower layers (as well as standardized C++ libraries). This slightly increases the cost of adopting Stroika for something small (because pulling one thing in pulls many things in), but then pays dividends as you use it to accomplish a second or third task.

• Stroika v2.0 is very stable, nearly complete, and requires C++14 or later. Stroika v2.0 is used to power a wide variety of open source and commercial applications.

• Stroika v2.1 is more actively evolving, and requires C++17 or later.

• Stroika v2.0
  Regularly tested on x86, arm, gcc5 thru gcc8, clang 3 thru clang 6, XCode 8 thru 9.
• Stroika v2.1
  Regularly tested on x86, arm, gcc7 thru gcc8, clang 6 thru clang 7, XCode 10.

• Vanilla make based builds
• Portable API (targets windows/mac/unix), and multiple processors

For more details on individual release changes, see:

    Release-Notes.md

"Getting Started" build instructions can be found in:

     Documentation/Building Stroika.md

Looking through the samples is also a good way to start:

    Samples/ReadMe.md

Please report bugs at:

    http://stroika-bugs.sophists.com