Explore insights on real-time edge computing, AI, and cloud solutions. Learn how our technology optimizes performance across industries.

Blog

At Macrometa, our mission is to make every developer a hero. What developers build is just as important as how they build it. Developers need their applications to perform at super low latency, even at scale. And it needs to be secure. And without all the costly infrastructure. The team at Fastly shares this vision, and that’s why we’re happy to announce that Macrometa is now a part of the Fastly Compute@Edge partner ecosystem.

Compute@Edge, Fastly’s serverless compute platform, helps developers explore new and innovative edge use cases. The partner ecosystem takes this a step further by featuring seamless integrations with other innovative companies across a wide variety of categories. Developers can now build on Compute@Edge and take advantage of Macrometa’s low-latency 

To see this integration in action, we’ve developed two sample applications built on Fastly’s Compute@Edge: A video streaming platform affectionately called Edgely + and a dashboard to track Fastly’s Real-time Log Analytics using the Macrometa 

The newest video streaming platform – Edgely +

Edgely+ from your friends at Fastly and Macrometa <3

Our video streaming platform shows what happens when you combine a super-fast, globally distributed database with Compute@Edge. Don’t just search for Keanu Reeves, refine your search by Keanu Reeves and Winona Ryder movies. There’s a few ;)

Real-time log analytics with Fastly and Macrometa

In this tutorial, learn how to use Macrometa’s pub/sub, event processing, and log analytics in real time using our Stream Workers and Query Workers (Javascript and SQL functions as a service). Ingest logs and process them to produce real-time charts and dashboards without sending any data into Splunk or Datadog (and maybe save some $$ while having fun programming for the edge). See HTTP latency, response count, response size, and unique visitor traffic - all right now.

We’re thrilled to be a part of the Compute@Edge partner ecosystem and can’t wait to see how developers build the impossible app with Fastly + Macrometa. Show us what you create by tagging us on 

Fastly Partners With Macrometa For Compute@Edge Partner Ecosystem

In 17.7, we’ve introduced a feature that allows users to create fabrics for multiple regions in the Macrometa GDN. GeoFabrics gives users more control over where their data can be stored and accessed.

In the past, new Macrometa users have had two options: access to 

 global regions or create a local collection that doesn't replicate to all regions. This had two downsides:

Not every application needs data to go to all regions, and in some cases, not all data should

Limiting to a single location/region is too restrictive

GeoFabrics give users the ability to use a subset regions, all based on their own criteria and not pre-generated (such as US, Europe, or Asia, for example). GeoFabrics helps GDN users not only comply with local data regulations (such as 

) but reduce read/write costs associated with global replication. GeoFabrics offers more options for where data should be stored/accessed, and this flexibility is offered via a simpler on/off switch. Users now have more control of data and the costs associated with reads/writes of that data. Just select the regions you need and we'll handle all of the ops. Better yet, GeoFabrics functionality is available to all users (no phone calls, emails, or signups required 😉).

When a user creates a new GeoFabric, the Macrometa GDN generates a specific global URL, and a set of regional URLs for that fabric. This fabric global URL provides geo-routing capabilities, so a request to this global URL will automatically get routed to the closest geolocation - relative to where the request was issued.

Tenant and fabric-specific URLs are essentially alias DNS records that map to the federation global/regional DNS records of the GDN. These are automatically created based on where the tenant/fabric is created. From there, all corresponding alias regional DNS records for this tenant/fabric are created on the Macrometa cloud DNS service. A unique global DNS record is created for that tenant/fabric, containing all of its alias regional DNS records, and configured with geo-location routing.

Macrometa tenant/fabric global URLs follow a specific naming convention: [name of a sea animal]-[CRC32 hash of the tenant/fabric combination + the DNS hosted zone name].

To illustrate how a tenant/fabric global URL is generated, we’ll walk through a typical tenant signup workflow and the creation of a GeoFabric spanning three locations.

 and clicking on the verification link in the confirmation email, the tenant is created along with the unique global DNS record.

Once logged in, the user is redirected to a page with their unique global tenant URL. 

Note: All edge locations are selected by default.

Now that this tenant is accessible, we can create a geo fabric for this tenant: Let’s create a fabric spanning two edge locations: on 

Upon the successful GeoFabric creation, we can see that a unique fabric global URL, along with its unique regional URLs, is also created. Notice that only two regional URLs are currently available (with toggle on), and the fabric global URL will only route requests to either edge location, based on the geolocation of the originating requests.

Fabric global/regional URLs, note the regional URL for Mumbai, India is currently disabled

There is an option to enable the third region: 

 for the fabric, effectively expanding the geo fabric to this region by creating the fabric in the Mumbai edge location, and enabling the geo-routing to the Mumbai regional URL on the fabric global URL: 

https://manta-58abf7ad.paas.macrometa.io/

The toggle button next to the now disabled Mumbai region can be switched, and it will generate a support ticket to Macrometa, notifying the platform administrator to add this region to this geo fabric on the customer’s behalf.

All of this happens in just a few steps. Watch it in action:

How does a tenant/fabric global URL work?

Overall, the tenant/fabric global URL is built on the existing federation global URL of the GDN, with its geo-routing capabilities. In addition, the global URL feature is expanded to allow the customer to create a fabric with a subset of available edge locations from the GDN, along with a unique URL for the fabric. Any request made to this unique URL will get routed to the closest location of the fabric

When a tenant/fabric is created/updated/deleted, the tenant/fabric global URLs are automatically created/updated/deleted on Macrometa cloud DNS service, along with necessary health check records, geolocation traffic policy records, etc. These DNS information are also maintained as a part system collections of GDN database.

Typical ways to generate a tenant/fabric global and its regional URLs:

During the sign up workflow of a tenant: a unique tenant global URL is generated, along with its regional URLs; customer is automatically redirected to the tenant global URL after successful login in to GDN.

Tenant global URL creation during tenant sign up workflow

Tenant creates a new fabric, and selects available edge locations for that fabric. The fabric global/regional URLs information are displayed under “GEO FABRIC” page.

Fabric global URL creation during fabric creation workflow

After a fabric is created, the tenant has the option to enable/disable a specific location for that fabric, resulting in this location being added/removed from the geo-replication; the fabric global/regional DNS records are also updated accordingly in the Macrometa cloud DNS service.

Why do we need the tenant/fabric global URL?

Many new Macrometa users didn’t need to use ALL regions provided by GDN, at least initially. Requiring them to use a static list of ALL regions added unnecessary friction for new users.

Similarly, some customers prefer to isolate the data to only certain regions for regulatory reasons. Ex: GDPR, CCP etc.

 the geo-routing capabilities of GDN. There had to be an option other than ALL or one.

The GeoFabrics feature bridges this gap: customers can use a single fabric global URL that provides geo-routing capabilities to direct the request to the region closest to them, without resorting to the current approach. With a tenant/fabric global URL, customers can get the geo-routing capabilities of the GDN without having the tenant or fabric running on 

Customers also receive a uniquely identifiable global URL per tenant, and one unique global URL per fabric created by that tenant, which can be used with the customer application, along with the GDN drivers. They can use a single tenant/fabric global URL to direct requests to the appropriate edge location, without having to resort to using any regional specific federation URL, i.e. “

GeoFabrics allow us to solve a core issue for first-time users but also allows for users to better control how and where they access their data. Having more control of data is a huge priority, not just for Macrometa users, but for everyone. We’re happy to provide this level of granularity without additional operations or infrastructure required from the user.

Data geolocation is not a new feature, and restricting data to specific regions is especially not new. What makes GeoFabrics different is that it's an improvement to our existing platform and makes the Macrometa GDN even more flexible than other solutions.

While DynamoDB has a max of 5 regions, Macrometa can provide a much bigger range, depending on your data's unique requirements

Fauna Regions allows users to restrict data to certain locations, but those regions are pre-determined (US, Europe, Asia, for example)

Google's Cloud Spanner offers multi-region support, but latency can increase with each node and data migration is...sticky, to put it mildly

 We’re a global data platform that lets users create geo-distributed databases that work in unison without any ops, and GeoFabrics help us do better at it.

Introducing GeoFabrics

In 2010, as I sat watching the FIFA World Cup with friends and family, an octopus named Paul was the topic of discussion. Paul had gained worldwide attention as an animal oracle due to its amazingly accurate predictions of the results of multiple soccer matches. I was captivated too.

The intersection with Macrometa started to happen when I thought about distributed systems, especially a 

. There are all these parallels between a good distributed system design, and the biology of an octopus: a good distributed system has a shared nothing architecture. It is highly reliable due to built-in redundancies hence no single point of failure, similar to the physiology of an octopus, which has multiple hearts and multiple brains.

Macrometa’s decentralized architecture has no single point of failure.

What's even more fascinating is that the octopus’ brain is distributed across its entire body, giving it the ability to articulate each arm independently. So, you can imagine if an octopus was a musician, it would simultaneously be able to play diametrically opposite instruments with its arms, as each one has its own brain, or dedicated processing units. This boggled my mind.

All of that processing capacity gives the octopus even more superpowers, such as camouflage. Octopus camouflage is not only limited to color blending, it can also replicate the texture of its surroundings in the most beautiful and creative ways, while also using these changes to communicate. The engineering of these uniquely intelligent cephalopods is vastly different from anything else on earth.

Just like the octopus, Macrometa’s converged multi model data platform is unique and powerful, and it delivers users superhero-like ability to develop amazing things in a fraction of the time it would take going the traditional routes. 

Our architecture is so fundamentally different from anything else that has ever been built to handle data in the cloud.

Just like the world deserved a better way to choose world cup winners, the world deserves a better way to build for the cloud. Start building your impossible application and let Macrometa be the brains in its appendages.

The Octopus And Macrometa

My professional life during the pandemic has been interesting (to say the least). Reflecting on life these past two years, I’ve realized I’ve had some amazing experiences and accomplishments: I’ve been through an acquisition, led some systems integrations, and managed a team during hyper growth. So why did I begin getting the feeling that something was missing? After some much needed introspection, I realized I was missing the joy of learning and doing something new every day.

That's why I am so excited to join Macrometa as its first Program Manager! I am also looking forward to supporting Macrometa as it grows to become the fourth cloud titan.


The largest factor for me was the culture - the people and the 

 they embody. Having experienced what an amazing, kind, and supportive work culture feels like, versus one that is overly demanding and unenjoyable, I knew I had to find the right culture fit to be happy. I could find meaningful work where I learn new things, but if the culture wasn’t right, I knew I wouldn’t be happy. 

Not only are they incredibly smart, they also truly embody the core values – Honest, Humble, Heart. The culture they create is one of trust, one of learning, and one of compassion. This is so important to me because culture lays the groundwork for how successful a company can be. I see that same culture when I meet someone new in the company.

The next important factor for me was the ability to learn and grow. Startups tend to move at the speed of light which means I also get to grow at that pace. While I don’t see myself becoming a full-time developer, I can already say I have learned a ton and I am only on Day 10. I get to learn technology and grow with the support of an amazing team.

Lastly, it’s always been important to me to be in a role where I believe in the company, the mission, and the vision. 

 is at the core of our technological future because it brings data closer to the location where it’s needed. It has such a wide range of applications from streaming services to telemedicine to autonomous vehicles. But more so, the company’s mission to “make every developer a hero” is what spoke to me. Our product will make globally-distributed app development and deployment simple and instant. I want to be a part of making that happen and leading us into the future.

I am beyond thrilled to join Macrometa on this journey!

Why Roma Shah Joined Macrometa

The themes around 5G in recent months have focused on how the reduced latency, high reliability, increased connectivity, and large bandwidth provided by 5G will disrupt industries. But the promise of 5G is only part of the story. The real value of a technology is not its attributes but what that technology actually delivers to people. There's a reason why internet infrastructure companies don't have the same market capitalization as FAANG companies.

When I read about a 5G use case claiming to disrupt the status quo, three questions come to mind:

 For some use cases, 50ms-100ms improvements in latency isn't going to matter much.

Can you do the same thing with existing wifi or cloud infrastructure?

 You can deliver many use cases from the cloud without sacrificing needs or user experience.

 Some critical use cases would be better off to just do data storage and processing on the device itself.

My experience is that many use cases lose their relevance to 5G once you start asking questions. So which use cases actually make sense for 5G?

Use cases dealing with Computer Vision (CV) and 5G-enabled cameras are an intriguing candidate. CV is a field of study that uses 

 techniques to help computers “see” and develop context around digital media like photographs and videos. Many use cases like quality control, change or object detection, etc., fall into this category. This category's suitability to 5G makes sense to me because

CV use cases are often real-time in nature and will immensely benefit from reduced latency.

CV use cases produce a lot of data (video streams), but 90% of it is noise. It's poor economics to send all that noisy data to the cloud, assuming one has the capacity to transmit.

Moving data and compute to a 5G edge will reduce the cost and improve the battery/longevity of the device.

 and stadiums are multi-faceted. On one hand, 5G reduces fan frustration because it can handle more users, and the extra bandwidth allows fans to receive or send large amounts of data with very low latency. In addition to reducing frustration, 5G can even heighten fan experiences with features like augmented reality. Additionally, use cases dealing with large crowds for other events and conferences make sense to me because

Stadiums and sporting events bring thousands of people and devices into a relatively small area. Providing ideal connectivity and bandwidth over 4G or wifi to provide rich experiences just isn't possible.

Real-time crowd management is another significant factor in this category (estimating queue wait times, tailored updates, social distance monitoring, crowd analytics, etc.)

Use cases dealing with mobility like public transportation and drones are another excellent candidate. 

 have become invaluable assets for end-users, enterprises, and governments, and much of this technology is helpful for companies testing autonomous aerial transportation as well. They make sense because

Public transportation involves both mobility (i.e., increased connectivity) and large crowds. Providing continuous connectivity and a large bandwidth to meet a crowd's needs is not something you can do over the cloud or wifi.

Drones involve both mobility and a lot of noisy data. Providing continuous connectivity and processing of noisy data at the 5G edge makes sense and is cheap. Also, 5G edge will enable drones to share computing resources (i.e., device offload), reducing their cost and increasing their stay in the air longer.

 are just as much about generating data and optimized workflows as they are about making things. Use cases dealing with smart manufacturing, factories, and construction are good use case candidates for 5G because

Smart manufacturing, factories & construction involve many devices/robots doing real-time monitoring, learning, and actuating in a small space. A lot of the generated data is noise. So it does not make sense to send to the cloud. A better alternative is to pool the resources and process this data at the edge. That will reduce the cost of the devices & improve their longevity.

I am not fully sure about this category's applicability to 5G, though, i.e., one can also achieve the above benefits by utilizing Wi-Fi. 5G provides more security out of the box and network slicing compared to Wi-Fi. So that could be the reason to use 5G.

 is empowering game developers to create new digital experiences. A 5G use case for gaming makes sense because

Improved bandwidth and lower latency creates a better multiplayer experience or enhanced cloud gaming delivery.

5G's high reliability means games can go uninterrupted, regardless of where the player is in the mobile network.

As a small thought experiment, think about a photograph you have seen or liked recently. Chances are it is a color photograph.

When Kodak introduced a 35mm camera in 1934, no one called photos "black and white" photos. 

. When color photos were introduced, only then did people start differentiating between the essence and attributes of a photograph. Suddenly photographs were either color or black and white. Over time, black and white photos became a unique case, and color photographs became the standard.

To me, 5G NSA or SA today is a lot like photographs in 1934. If you dig deeper into the use cases above, 

 is the common thread. These use cases are either about

Volume & velocity of data (i.e., bandwidth) or

Mobility of data source (i.e., mobility) or

Reliable data access (i.e., reliability) or

Time to process & actuate on data (i.e., latency).

 to process an event or request and take action. The context could be about the

The environment in which the event/request and processing happens or

Relationships between itself & its peers or

Connections between its past and present or

Configurations & Constraints around processing the event/request etc.

Current cloud native data platforms can't meet all of the needs of 5G. These use cases, to reach full potential, need 

 decentralized data platforms to bring much needed color.

Please feel free to share your perspectives. What other 5G use cases are showing promise?

Building applications the edge native way

Telecom providers need to be more than just data pipe providers

The Top 5 Use Cases For 5G

Gaming has the potential to be a killer application for 5G. But it must bring something new to the industry.

We have to look beyond reusing the technology created before the mobile broadband era. That must not be the extent of our ambition.

We must empower developers to create the next-gen experiences of the 5G era. We can provide a 5G cloud, one that is both 5G native and 

. Developers need a platform that can not only reduce lag beyond human perception but also process game data in real-time.

5G is empowering game developers to create new digital experiences.

Do you remember when you fell in love with video games? I remember when it was for me. I had plugged the new network adapter card into my Sony PlayStation 2. Connected it to my 600K Cable Broadband Modem (fastest connection in the UK at the time). I then fired up SOCOM US Navy Seals + Headset :) and joined my first 8v8 multiplayer battle. A few games later I received an invitation to join a faction called the Disposable Heroes. In no time, I was playing competitive organized events and leagues and my world was never the same again.

What amazing formula connectivity and gameplay make. Much greater than the sum of their parts. The original product marketing for the PS2 Network adapter card was as follows:

“The World at your fingertips. Tackle, shoot, frag, and outwit anyone, anywhere, anytime. With the Network Adaptor for PlayStation 2, just about anything is possible. Start your own rivalry across the nation with trash-talking opponents you’ve never met. Experience the best in live competition. No two games are ever alike”

SOCOM for PlayStationPowerful messaging (at least to me back in 2003). After my experience with SOCOM, I didn’t play another game for quite some time. I became addicted to online play. With every new game, I would check to see if it had those three little words written on the cover: “with network play”.

That promise of playing anyone, anywhere, and anytime was a bit of a stretch. I wasn’t going to be able to carry my PS2 around with me to play it “anywhere”, and “anytime” was usually when I finished work. As a side observation, the first version of SOCOM actually supported LAN parties. The precursor, or at least an unknowing nod to the future of Esports events? No latency, or lag issues, no unfair advantages. Skill vs Skill. V.cool.

The developers of SOCOM had a vision for the experience they wanted to bring to console gamers. They nailed it.

5G gaming “The World at your fingertips...”

When I contemplate 5G and gaming, I think back to SOCOM. That promise of a game “with network play” that would open up new worlds and experiences. Game developers in 2021 should see 5G with that same sense of vision and opportunity. Just like developers did in 2003 for the PlayStation 2 network adapter card. An enabler of new experiences.

I want my daughter to have that same “wow” moment provided that I had. But in truth, I want it for me too. :) “The World at your fingertips”

 combined have such great potential. But we need to get it in the hands of developers in a meaningful way. We don’t even need to wait for 5G Standalone – Non-Stand Alone with edge computing is a great start. Improved bandwidth and lower latency are attributes that provide a better quality of service (QoS), which translates into a better multiplayer experience or enhanced cloud gaming delivery. But how do they provide that “wow” moment to the gamer? Something they have never experienced before. What is the compelling event or new experience that is being enabled or introduced?

5G is not enough for next-gen gaming on its own. 5G gaming platforms must reduce lag beyond human perception. And they have to do this 

 limiting the player pool. In fact, they need to expand the proximity limits of who can play. Developers need a platform capable of processing more game events in a single “tick”. Data processed closer to gamers that enables game developers to create new and richer experiences. Derived from insights generated from gameplay events in real-time. 

The 5G era of gaming needs to be much more than lower latency play. 5G should be the standard all future mobile gaming platforms have to beat.

Current games are supported by simple client-server-based architectures. 5G will have to support a polyglot approach to gaming traffic protocols and provide a transport layer that transforms game architectures into an event-driven architecture.

This will enable game developers to add new capabilities to the game in an agile manner, while also reducing complexity and operational costs.

A 5G database must enable game developers to leverage historical and real-time context. This data will allow developers to incorporate rich insights, personalization, recommendations, and intelligence into the games they create.

 will introduce rich leaderboards and player statistics, as well as identify patterns and trends in real-time from their game worlds.

5G will support serverless functions and containerized game logic. Artificial Intelligence to enhance the gaming experience, for example, there will be more sophisticated systems for identifying cheaters and identifying player abuse and checking the gameplay in real-time. Developers have the ability to take action in real-time on the game world mechanics.

Imagine more customized matchmaking systems based on real-time data and 

 that reduce queue times. Developers will understand a player’s real-time mobility within the mobile network and make sure they have the best experience.

With data and imagination, anything is possible.

I love this visualization because it shows the market history from 2020 all the way back to 1972. In 2020, consoles generated $33B, PC $40B, and Mobile $85B. The types of games that launched between 2018 and 2020 are quite telling. They are mostly free-to-play, or freemium. They are battle royale and massively multiplayer. They are on mobile devices. They are also moving beyond traditional gameplay and offering new in-game-world experiences.

This is why I say I hope for more from 5G and 5G for game developers. I hope that 

 take a leading role in building on next-gen gaming technology. I hope they enable cross-over and extension into other industries and experiences. 

Online Esports. Interactive gaming. eCommerce. Anti-cheat and abuse-detection. Streaming. Vast multiplayer worlds, and augmented realities. Experiences that can be accessed from anywhere across the 5G network. Powered by the real ability to access, process, and act on 

. And it's all within our reach. Who knows, they might even be able to build their own metaverse.

I believe that 5G has the potential to enable that “wow” moment for mobile gaming. Just like the network adapter card was for my PlayStation 2. “The World at your fingertips”

And yes the vertical axis should be inverted, well it depends actually ;-)

 if you'd like to talk more about 5G. Maybe we can take a call whilst playing some CoD :) (I just started Naraka Bladepoint, so maybe on there).

How 5G Gaming Will Change the Industry

2021 will be a memorable year for so many personal and professional reasons. It marks the end of many journeys as it marks the beginning of new ones. There are moments in life when you stop, look back, reflect on the past and double down on what comes next. I found myself in this moment and being at the right place at the right time as I crossed paths with Macrometa.

Could I find another opportunity to match or top my 11 year journey with Gazzang? I began writing its very first lines of code on nights and weekends, and saw it through Series A and the acquisition by Cloudera. I watched it become a unicorn IPO and growth north of $800 million in ARR. I was happy with my journey as VP of Engineering and CISO to CIO. But, like getting off a rollercoaster, I felt I needed to do it all over again.

I had heard all these great about Macrometa – but I was a bit skeptical. As a security person, you have to be skeptical about pretty much everything. As I talked to the founders, saw the technology, and learned more about their early customers and successes, that skepticism quickly faded away. As I dug deeper, I continued to be amazed and started to see that Macrometa was at the beginning of something big.

After 30 years of building software and solutions across different operating systems, coding languages, databases, user interfaces, APIs, data centers, clouds and containers, you name it, I have seen many technologies come and go. The ones that endured are the ones that were embraced by developers, easy to use and maintain, stable, and trustworthy. In Macrometa’s 

 (GDN), I see all the right ingredients for developers to quickly, securely, and seamlessly create the technology that will drive a new world. A world that does not believe in barriers, that is globally-distributed, that processes information in milliseconds, where —living on the edge— takes on a whole new meaning.

I am thrilled to join Macrometa as CISO/CDO/CIO and will work tirelessly to win the trust of our customers, providing a secure and safe place to process their most sensitive and critical data. I will also keep confidentiality and privacy at the forefront of all data analytics, data engineering, and data science that will continuously improve the Macrometa platform. I will also be helping Macrometa grow and mature to its full potential. As a Macrometan, I will be a colleague, friend, and voice for diversity and inclusion.

While I have been part of several startups in my career, I have never been as excited as I am for Macrometa. The feeling is hard to describe, being part of a team with so much energy where everyone is bringing the best of all their previous experiences and coming together to build something big and new.

The future ahead is ripe for new technology breakthroughs in space, renewable energy, telemedicine, technology, and quality of life. I am so excited to see how Macrometa can become an important contributor to these breakthroughs.

Thank you Macrometa for this opportunity.

Why Eddie Garcia Joined Macrometa

I’ve been involved in some great edge-related activities over the past few years. Some of these activities have been focused on Infrastructure as a Service (IaaS) or orchestrating workloads around a distributed cloud. While IaaS and workload orchestration are important parts of an edge cloud solution, where does the platform for developers fit into all of this?

In my last blog post, I said that building applications for the edge will require a different set of tools. The edge (and the 

 in the most extreme sense) is about real-time performance and an improved experience for humans and machines. It’s this concept of service immediacy that goes beyond industries.

Even though there are many applications and technologies residing in the centralized clouds, they don’t always translate into workloads that make sense at the edge. The main reason a traditional 

 is because it doesn’t face the same barriers as distributed architectures. Even if they technically can run at the edge, that doesn’t mean that they’re optimized for the edge. 

, especially mobile network operators with 5G, are transforming their business in two main ways. The first way is technical, i.e. network transformation and evolving from the traditional physical network functions approach to network deployment to a virtualized approach (VNFs and now CNFs). The second way is monetization, i.e. business transformation and how they monetize that network asset and capabilities to attain a return on their investment.

Telcos are essentially becoming edge technology services with the goal being to offer their unique value proposition in the form of network-centric edge cloud services.

Telcos that focus their edge cloud services on 

 and service immediacy are going to be more successful and fit into the technical and business requirements of modern distributed systems.

What application developers need for the edge

Rather than simply hosting application workloads created by others to run at the edge, 5G mobile network operators can become enablers of solutions. But first, they’ll need to address the needs of enterprise application developers at the edge. Telco edge cloud providers need to consider three main concerns: Performance, developer velocity, and costs. 

, low latency real-time insight, and actuation. Developer velocity isn’t just about the speed of development or deployment, it’s about the rate of developer adoption as well. The costs also have to be worth the investment – does the platform’s cost result in tangible performance and increased developer velocity?


To meet the demands of enterprise applications and the developers that create them, network operators need to support a polyglot approach to enterprise architecture primitives. Imagine a platform that embraces an edge native approach to application development. Developers can leverage 

 computing to maximize the dynamic, mobile (migratory) nature of deployed software services at the network edge. 

How Macrometa overcomes obstacles of the edge

The edge is born from the principle that data has gravity. Basically, the existence and mass the data has, in itself, attracts processes and workloads to it. Like any large body that has gravity, other objects are attracted to it and sit (and therefore operate) in its orbit.

At Macrometa, we have built an edge cloud platform that embraces the principle that data has gravity. For example, if insights need to be generated in real-time, our platform enables a distributed approach to application design that brings workloads, 

, and application logic to where the data actually is. The mechanisms required to intercept, capture, process, and manipulate data have everything they need.

Telcos and mobile network operators that work with Macromenta are able to deploy an application that is natively low latency, built for high-velocity data ingestion, manipulation, and actuation. Data replication, query, processing, and insights can be performed and generated across the operator’s footprint with near-instantaneous synchronization, or even globally (off-net) within ms.

 is built around persistent streams and real-time stream processing via our Stream Worker technology. Our Stream Workers allow developers and Telco enterprise customers to define sources and sinks, tables, processors, and javascript functions. Stream Workers are extremely powerful in real-time event execution in an 

 / ELT architecture. Stream workers give the developer the power to collect, shape, analyze and act on application in-flight data and data at rest.

The platform also provides a stateful container runtime that is distributed across a network topology with both compute and FaaS capability.

Hopefully I’ve managed to explain what we have in our platform, its features, and how our Telco customers are using it to offer real-time edge cloud services. It’s pretty exciting stuff.

We (Macrometa) have telco customers today who are right in the middle of this transformation and using the Macrometa platform to build their edge cloud services while addressing complex use cases like connected vehicles, 

 you can find tons of demos and tutorials, from simple “hello-world” type applications to more complex ones like 

. We also have all the documentation you need to get started to familiarize yourself with our platform and build your own global edge applications today.

How To Build Applications The Edge Native Way

Today, we have many hyper-scale, distributed data platforms that can handle big data workloads with elasticity and simplicity. This simplicity comes from the fact these workloads run within a single data center in a single, centralized region. As long as those resources needed to scale are available within that same data center, everything scales as it should. But we’re entering a new age of data decentralization enabled by powerful next-gen devices, 5G networks, advances in 

, AI/ML, and the current geopolitical trends for regulating sensitive data.

This new world requires a new cloud –one that is distributed rather than centralized. The problem is that cloud native approaches that worked well in our centralized architectures 

 in this new paradigm of dispersion and decentralization. 

Edge cloud needs an edge native approach that is designed to meet the challenges of the edge, built for distributed architectures, and optimized for decentralization.‍

The centralized approach doesn’t work because it doesn’t face the same barriers as distributed architectures. Unlike single region architectures, decentralized architectures need to deal with these five following challenges:

Large network latencies with 100s of milliseconds

For any data platform architecture to be truly edge native, it has to effectively address these five primary challenges of edge.

Archive