The first AMA based upon ‘Scaling’ took place on the 15th July with Jack, Olivier and Colby. Since our core objective over the past few months and into the near future is centered on maturing and efficiently growing the protocol, the topic of scaling is interesting in many ways.
Here are two Questions and Answers we thought you might find interesting:
Q — Deofex
In your recent communication you wrote a lot about the digital twin concept you’re building. It sounds like a great concept and from what understood about it until now it feels like the system can contribute to scaling the amount of customers (ticket companies) you can onboard.
From what I expect the digital twin concept will provide an API where current systems can talk to. If this assumption is correct I have the following questions:
- Are there a limited amount of ticket systems on the globe and will you provide plugins/support for these systems to make it possible to talk against the API, or is this something customers have to do their self?
- If there are a lot of ticket systems (external, or maybe even in house developed), do you expect that ticket providers and their ticket program partners/in house developers can integrate the digital concept fast, or will this be time consuming and complex process?
A — Jack
Since we’re on the topic of scaling this week, these are interesting ones to answer through that lens. Without going too far off track, the mission is to become the ticketing standard worldwide, and the most obvious way of measuring that would be through market share. While I can’t point as a deep study, we can say with a high level of confidence that most ticketing volume worldwide would not be done through standard platforms and systems, where the vast majority is in-house and custom.
For that reason attempting to optimise for ease of integration to any custom system is the focus. It likely wouldn’t be available at the time of launch, but we’re keen to offer SDKs/libraries in a couple of key languages to wrap our APIs to remove a couple of integration steps, where the more advanced integrations can still call the APIs using a HTTP client of their choosing, and parse the responses how they wish rather than relying on the SDKs.
I wouldn’t go as far to say that avoiding integrations with systems isn’t a target, but there’s a cost of maintenance that you see when having to upgrade and manage X amount of plugins, then X+1, then X+2 as you add more — I’m not convinced market share is dependent on this, and it’ll be simple enough without it.
Will it be quick and easy? Yes!
The APIs will be well documented and explained, along with integration guides, quickstarts and code examples. It also helps that with on-chain data storage being expensive it results in a relatively simple data model which then leads to a relatively simple API suite (simple in complexity, not in value).
Q — Mister_ThreeTime
How has scaling impacted specifically event financing? Are you guys looking to roll out more features at first launch, or did you run into other problems during the process that you’re looking to solve when you get more people onboard?
A — Jack
Thanks for asking this one, it’s a really important one to address. From the previous blog its clear that the level of explanation around the dependencies and trade-offs didn’t scratch the surface.
You can slice scaling a load of different ways, all with slightly different approaches and optimisations — but in short it’s not just about growing the team. That’s one of the most visible ones but isn’t the full scope.
I’ll hold my hands up here and say that when I think of scaling I often think of everything but hiring, whereas that’s not really what has been conveyed so far.
We need to scale up our market share, scale up our maturity, scale up our documentation, scale up our service reliability, scale up our agile process, scale up our product discovery processes, scale up our development practices, scale up our market share and treasury, scale up our feature set, scale up our community involvement, scale up our business networks, scale up our hiring and onboarding strategies, scale up our infrastructure, scale up our internal tooling, scale up our layer 1 networks.
This wouldn’t even be a complete list (not even close, but hopefully you get to see where I’m coming from).
Throw all of these together it ultimately takes time to execute well. We don’t over-optimise for perfection and trust each others instincts and judgements but applying all of these scalability concepts does take time.
It’s worth talking about what the Digital Twin enables also; it’s the first completely tailored solution for existing ticketing companies to write their existing volume on chain, with very little integration hassle and a high amount of reliability.
There’s incredible promise with a solution like this and we’re being very uncompromising when it comes to delivering something that you can point at and say that it is the global standard. Without a shadow of a doubt there are elements of this that weren’t clear when predictions and timelines were previously set.
Scaling also means being able to do more than one thing at a time well, and this is a reality we’re dead set on moving towards. Not hitting expectations is something we wish to avoid at all costs so we’re not ready to set out a new timeline for this just yet, but we’re definitely not sitting on our hands either and we’re hoping to be able to dive more into this over the coming quarter.
More Scaling Q’s & A’s
Of course it wouldn’t have been a scaling AMA without diving into further detail on the efforts of scaling everything, the outcomes of scaling we’re aiming for, how GET fits into the puzzle as we go global (and decentralised) and last but certainly not least — building a complete infrastructure that embodies the future of ticketing, for fledgling ticketeers and established ticketing companies.
It’s indeed this last point that has captured a large chunk of our attention and resources, as we are finding more and more reasons to believe there are ample opportunities in serving not only those wishing to get set up with their own ticketing operation, but also those entities who might be looking to move with the times.