What is Chronix?
What is IronDB?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Chronix?
Why do developers choose IronDB?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Chronix?
What are the cons of using IronDB?
What companies use Chronix?
What companies use IronDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Chronix?
What tools integrate with IronDB?
Sign up to get full access to all the tool integrationsMake informed product decisions
We've always counted on SQL Server as our database backend. It has served us well over the years. It isn't the cheapest part of our stack, but with the plethora of tools provided by 3rd parties, we have found an incredible and scalable method of keeping our data available and easy to maintain.
Defacto, industry standard for backend relational databases. Entity Framework makes designing, migrating & maintaining SQL Server databases a breeze. LocalDB is especially helpful during development.
Our core systems that we integrate with are using SQL Server 2012 / 2016 database servers. We use database views on core system databases to help build our domain model.
Main transactional database. SQL Server 2012 Enterprise with AlwaysOn Availability Groups for high availability and disaster recovery.