|
|
 |
Why Not Choose Encirq?
While there are lots of good reasons to choose Encirq, there are some situations where Encirq may not be the best choice.
- No Need
You already have all the engineering resources, time and expertise you need to solve your embedded data management challenges.
- No Interest
No interest in improving software reliability or reducing development effort, time and costs.
- Works OK Today
Your data management code and/or third-party database works OK and there is no interest in improving reliability, performance, memory usage, scalability or portability.
- Need a “Full” DBMS
You need a full-featured, desktop-style, client-server relational database management system and can easily afford adequate computing power and memory resources to support it.
- Full HA Support
You want out-of-the box high-availability, mirroring and fail-over capabilities.
- JDBC
Your apps are in Java and you “must” use a JDBC interface to a database rather than JNI.
- Tiny System
You have an 8-bit CPU and cannot afford the 30KB of memory or so for DeviceSQL Runtime Services to operate.
- No Budget
While we are committed to working with you on both engineering and budgetary problems, we cannot work for free.
Get to Know Encirq
If one or more of the above situations apply to you, Encirq may not be your best choice. But if quickly getting extremely fast tight, reliable code for managing data is important to you, you should get to know Encirq. Contact us today.
|
|
|
