The other day, I started working on a small project: creating an application that connects to an embedded circuit and transmits data. Meanwhile, I encountered some hurdles while coding, especially with communicating via Rest API, which can be a bit confusing. Anyway, I finally found a solution that really worked 🙂
As you know, embedded systems and C# are not the most common pairing. In fact, thanks to C#’s convenience and the flexibility of the .NET framework, such projects become somewhat more accessible. By the way, a few months ago, in a small project, I was using MySQL instead of PostgreSQL, and I was surprised by the difference in speed and performance. Of course, every project has its own advantages and disadvantages, which is also worth mentioning 🙂
In such projects, the most important thing is to design the API properly and establish clear communication. For example, initially, I faced some errors during API requests. While working with Dapper, query optimization became necessary. Beyond CRUD operations, transaction management was also important. However, I can say I experienced data loss in my first attempt. My own mistake 🙂
In conclusion, using C# in embedded systems seems very logical to me. With proper API design, data exchange between devices can be comfortably achieved. Despite a few minor mistakes, I managed to run everything smoothly and data flows started. Also, performance of the code is crucial, and it may require testing for at least a few hours. Plus, constantly trying new things and updating is necessary, or else it becomes outdated 🙂
Therefore, in practical, experience-driven projects like mine, such work is quite instructive. My advice is to always prepare backup plans and keep your code organized. Who knows, maybe someday, these small circuits will inspire big projects 🙂