I also believe that building my repository and data access patterns on a Scala codebase could yield good results, as #Spark and other #Apache projects are natively built in Scala. Hence, the support to consume and create solutions around them is very mature.

On the other hand, doing the calculations for another project using AWS Fargate, which might provide far more value in the market, is now set as my goal to ship and deploy. The learning here is that estimating costs is crucial for the viability of products.

I'm really proud about this implementation. Native support for this library for OTEL. It does still need a bit of work on the metrics, but looks solid so far.

PS: I did create and work on my own DDD and Event Sourcing library in Golang. I made it Open Source to share this code with everyone and probably refine this codebase with the help of others. #DDD #EventSourcing #Golang #OS

I'll soon work on a blog post about the instrumentation and provide a few examples paraphrasing Simon's talks on C4, its tooling, and how to use it.

"System Design - Building a Scalable Real-Time Blog Platform with Kafka and Cassandra" by Alejandro Sosa #DEVCommunity

"Comparative Benchmarking: ILP, A*, and Branch and Bound Algorithms in High-Throughput Scenarios" by Alejandro Sosa #DEVCommunity

"Open Telemetry: Observing and Monitoring Applications" by Alejandro Sosa #DEVCommunity

RT @elonmusk: Precisely

There is nothing I love more in development than planning, analysis, gathering requirements and creating a system from scratch.