“To SQL or not to SQL, that is the Question”

Part of an ongoing blog series discussing why we made certain technology choices.
By Jerome Pascua
Sr. Director of Software Design, ASD.ai

“If you’ve met one individual with autism, you’ve met one individual with autism.”

Dr. Stephen Shore

We’ve architected our software to echo this sentiment in the sense that we want each of our users to have the ability to tailor the app to the needs of an individual.

So what does that mean for us and our app?

Well, it means that we will need a data solution that offers us data flexibility and the ability to make changes as new discoveries are made. For example, let’s say that a care team on the east coast has been tracking a person’s sleep over several months. Then, someone on the care team notices that, when the tides are high the night before, the person wakes up feeling unrested the morning after.

How can I, as a software developer, enable that team to associate tides with data that they’ve already captured and with data they enter going forward?

Problems like updating database schema, data models, the data layer abstraction, and relational mappings can become time-consuming and difficult to document.

We decided on the use of NoSQL databases for the ability to build and adjust quickly. With NoSQL, we were able to implement a Document database structure that gave us the flexibility we desired. Insights and calculations can be focused on the individual and the data that’s important to them. Coupled with a proven cloud offering, we also gain performance and scaling features that can grow as our user base grows.

Most importantly, the data should be able to paint a picture of each individual as they are.

Rootines is available now on iOS and soon on Android. Visit our website for more information.

Leave a reply:

Your email address will not be published.

Site Footer

Sliding Sidebar