I've been fortunate to have had a professional life that has exposed me to many experiences. I've not just tried my hand at software architecture and engineering, but also have been a full time professional quantitative trader for many years. The majority of my trading was with Index and Currency futures on Chicago Mercantile Exchange (CME), as well as trading US equities.
Over the last few years the focus of enterprises has been on cloud computing, but increasingly the focus is shifting towards edge computing which provides benefit of low latency and real-time processing. But many real world edge applications require state to provide meaningful results whether that edge application is for:
At some point in the last 12 months, something historic happened quietly and right under everyone's' noses. Without much fanfare, the center of gravity for cloud computing moved from the centralized databases and compute in giant hyper-scale data-centers to the edge of the network where CDNs live. This tectonic shift changes the way you (dear developer) will build applications, APIs, and all things programmable in the months, years, and decades to come.
Let’s say you want to build an online multiplayer game that takes advantage of edge computing to provide low latency and a fast and real time user experience. These kinds of games are hard to build because you need to understand low-level networking inside game engines (like unity or unreal), and deal with lots of complexity when it comes to sending and receiving state data as well as storing it
Macrometa set out to create a platform that only companies like Google, Facebook, and Amazon have been able to build - a globally distributed data backend running in global locations to serve data to apps and APIs from the edge, closer to users and devices. With Macrometa - anyone can build apps and APIs that run distributed, cross-region, and multi-cloud and they don't need to know anything about concurrency, consistency, or mastering the arcane complexities of distributed systems.