aftonApi maintains sanity in the world of never-ending, shifting date/time formats by exclusively marshalling all date/time information using a string format. Therefore, no matter what kind of technical landscape you have on your end, you can assure that everything will play nicely together no matter what your preference is.

Is there a performance tradeoff for this? Well it depends on your load, and in the vast majority of cases it's not worth fretting over. The positive uplift for the tradeoff is the time and effort you will save when someone in your organization, or customer base, decides to throw a brand new date/format into your integration mix, along with the treacherous, shark infested waters of unmonitored time zone conversions, and then you have to spend hours, days, weeks to sort it all out.

Yes the tradeoff is worth it. aftonApi's dates as strings approach is simple, easy to understand, and all of your integration partners will be able to work with it very easily.