Viewing profile — jeyjeyemem

You can still strictly adhere to section III if you choose to - by only loading the environment variables, but Externalized Properties allows more than that if needed. By using Ext…

Definitely! There's no limit on what configuration formats Externalized Properties can support as you can implement custom `Resolver`s to retrieve from any source and format e.g. p…

It's more performant than other similar libraries such as the Owner and cfg4j which no longer seems to be actively developed at this point and others such as Spring's Environment a…

Externalized Properties was inspired by the The Twelve Factor Methodology's section III. Config. The goal of this library is to make it easy for applications to implement configura…

Externalized Properties is powerful configuration library which supports resolution of properties from external sources such as files, databases, git repositories, and any custom s…

Emissary really shines if performance is a top priority. The setup is more or less similar, you register a bunch of event handlers when initializing the library. The main differenc…

This a frequently requested feature. At the moment, it only handles in-process messages but allowing for persistent events is definitely in the roadmap. It's not built-in right now…

Yes, I am the author. I didn't know that, I'll give it a try. Thank you for the tip!

Emissary is a simple-to-use, no dependency, yet BLAZING FAST messaging library for decoupling messages (requests and events) and message handlers. Emissary aims to take advantage o…

https://github.com/jeyjeyemem/Xer.Cqrs Library was built to aid in building decoupled apps based on the Command Query Responsibility Segregation (CQRS) pattern. Some of the feature…