I have been using Ada for around two to three years mainly for customer support automation. I automate responses to common customer questions like order status and account troubleshooting.
I have been using Ada for a little over three years now, primarily in backend control systems and a few safety-sensitive services where predictability matters more than raw developer convenience. What stood out early was how much Ada catches at compile time, especially around type mismatches and boundary issues, which saved us from a lot of avoidable production bugs. I use it in a fairly demanding environment with strict uptime targets, where it consistently holds up well, making it one of those tools we trust for the part of the stack where reliability really isn't negotiable. My use for Ada is building reliable, low-level service components that handle device communication, telemetry ingestion, and deterministic processing, particularly where timing and correctness matter. Ada's strong typing and built-in concurrency model make it a very natural fit, especially for components that need to run continuously without memory drift or unexpected runtime behavior. I lean on it for the parts of the platform where stability is more important than rapid iteration. I have one example to share where Ada really made a difference: a telemetry processing service built in Ada for an industrial monitoring platform, ingesting roughly 1.8 million sensor events per day, validating them, and routing them into downstream systems with very tight error tolerances. After moving that workflow from a mixed Python implementation into Ada, we cut runtime exceptions by around 40% and reduced processing latency by just under 30%, with the biggest win being the service becoming much more predictable under load, especially during peak ingestion windows. Ada helps achieve that reduction in runtime exceptions and processing latency mostly through its language features, with tooling reinforcing the gains. The biggest factor is Ada's strong static typing and range constraints, catching bad states at compile time instead of discovering them through runtime exceptions in production. We benefit from explicit package contracts and stricter interface boundaries, reducing invalid data passing between components and eliminating a lot of the defensive error handling we used to write in Python and C. Latency improvements mainly come from moving the hot path into compiled, native Ada code, which removes interpreter overhead, cuts object churn, and provides much more predictable execution under load. Beyond the core services, we also use Ada for internal utilities, protocol adapters, and a few embedded system integration layers. A significant area of impact is writing deterministic interfaces to hardware-adjacent systems without needing excessive defensive code. We also use ALIRE to standardize dependency handling and simplify local environment setup, which makes onboarding much more streamlined and cleaner than older Ada workflows, giving us a pretty practical, modern toolchain around the language.
Data analyst at a healthcare company with 10,001+ employees
Real User
Top 10
Apr 9, 2026
Ada is a healthcare software that provides disease identification based on your symptoms. I receive many symptoms and questions from patients about their conditions because they want to book a visit and provide the reason for their visit. I have used it a couple of times to check what my son is going through when he had a fever and many different conditions. I put the symptom in, and it was pretty accurate.
Sr. FinOps Engineer at a tech vendor with 51-200 employees
Real User
Top 20
Dec 2, 2025
Ada serves as an AI customer support agent that drives our back end to help with customer success. I am mostly working on the back end, and the team responsible for setting up Ada handles the specific implementation details.
Ada is designed to streamline workflows and enhance customer interactions. It stands out for its ability to automate and personalize user experiences while efficiently managing information and inquiries.This technology handles tasks through sophisticated automation, reducing manual workload and increasing productivity. It's tailored to deliver personalized user interactions, significantly improving customer satisfaction. With Ada's powerful capabilities, businesses can seamlessly integrate...
I have been using Ada for around two to three years mainly for customer support automation. I automate responses to common customer questions like order status and account troubleshooting.
I have been using Ada for a little over three years now, primarily in backend control systems and a few safety-sensitive services where predictability matters more than raw developer convenience. What stood out early was how much Ada catches at compile time, especially around type mismatches and boundary issues, which saved us from a lot of avoidable production bugs. I use it in a fairly demanding environment with strict uptime targets, where it consistently holds up well, making it one of those tools we trust for the part of the stack where reliability really isn't negotiable. My use for Ada is building reliable, low-level service components that handle device communication, telemetry ingestion, and deterministic processing, particularly where timing and correctness matter. Ada's strong typing and built-in concurrency model make it a very natural fit, especially for components that need to run continuously without memory drift or unexpected runtime behavior. I lean on it for the parts of the platform where stability is more important than rapid iteration. I have one example to share where Ada really made a difference: a telemetry processing service built in Ada for an industrial monitoring platform, ingesting roughly 1.8 million sensor events per day, validating them, and routing them into downstream systems with very tight error tolerances. After moving that workflow from a mixed Python implementation into Ada, we cut runtime exceptions by around 40% and reduced processing latency by just under 30%, with the biggest win being the service becoming much more predictable under load, especially during peak ingestion windows. Ada helps achieve that reduction in runtime exceptions and processing latency mostly through its language features, with tooling reinforcing the gains. The biggest factor is Ada's strong static typing and range constraints, catching bad states at compile time instead of discovering them through runtime exceptions in production. We benefit from explicit package contracts and stricter interface boundaries, reducing invalid data passing between components and eliminating a lot of the defensive error handling we used to write in Python and C. Latency improvements mainly come from moving the hot path into compiled, native Ada code, which removes interpreter overhead, cuts object churn, and provides much more predictable execution under load. Beyond the core services, we also use Ada for internal utilities, protocol adapters, and a few embedded system integration layers. A significant area of impact is writing deterministic interfaces to hardware-adjacent systems without needing excessive defensive code. We also use ALIRE to standardize dependency handling and simplify local environment setup, which makes onboarding much more streamlined and cleaner than older Ada workflows, giving us a pretty practical, modern toolchain around the language.
Ada is a healthcare software that provides disease identification based on your symptoms. I receive many symptoms and questions from patients about their conditions because they want to book a visit and provide the reason for their visit. I have used it a couple of times to check what my son is going through when he had a fever and many different conditions. I put the symptom in, and it was pretty accurate.
Ada serves as an AI customer support agent that drives our back end to help with customer success. I am mostly working on the back end, and the team responsible for setting up Ada handles the specific implementation details.