Why we built on Serverless
Just a few months ago, we were in full preparation mode to launch a much-awaited, ambitious version of our robust SaaS Platform: Artifakt V2. Since then, we’ve taken big leaps towards our fast-approaching launch date by connecting, managing and scaling over 120 cloud architectures and applications. How? By building our V2 with around Cloud Serverless technology – a framework quickly taking on the role of industry benchmark for framework agility and resilience.
Over the next few weeks, we’ll give you a peek behind the curtain and tell you more about our own implementation process, as well as what it means to our users.
But for now, let us tell you why we chose to work with Serverless.
When it comes to computer networking and software, resilience is defined as “the ability to provide and maintain an acceptable level of service in the face of faults and challenges to normal operation.”
So it’s no longer best practice to put all of your proverbial eggs in one basket; distributed, autonomous and powerful networks diminish risk and allow distributed systems to quickly pick up the slack if one or multiple servers are faced with potential failures or glitches.
That means a faster, more seamless and secure push and publication process for clients and teams of all sizes – without the added friction of infrastructure management or lengthy ops. But don’t just take our word for it: see our latest status report.
We’re moving fast.
By implementing Serverless, Artifakt reduced its monthly costs by an astonishing 60%. A few different factors contributed to that dramatic leap, including Serverless’ pay-per execution model, which charges only when services are in use.
Labour redistribution also played a key role in minimizing costs. With Serverless infrastructures, stability and resilience allow for teams to streamline and accelerate every step of a project’s distribution process; from prototyping to iteration. In a tech landscape that propels innovative companies to fail fast and iterate constantly, reducing go-to-market time had a powerful impact on our bottom line.
Stronger resilience also means a dramatic decrease in the time, money and labor-hours spent troubleshooting or rerouting your data once an essential server inevitably acts up.
That reduction in maintenance work, of course, frees up more room and brainpower for the next big idea.
Like an Artifakt Store, for example.
While Artifakt has always allowed users to deploy and manage 13 applications across 4 different infrastructures, we’re now preparing to offer hundreds of highly curated ready-to-use applications through our Artifakt Store. That remarkable growth has required an essential shift towards a framework and logic that both scale and play well with others. Serverless has allowed us to meet this increase in demand without the added costs and complications of managing a server fleet. That means we can keep focusing on what matters most: growing and improving our Artifakt community and solutions.
Stay tuned: in the coming weeks, we’ll tell you more about what we learned implementing our own Serverless framework and what it’ll tangibly mean for our community of managers, developers, and devops. Curious to see how dramatically our Serverless shift could simplify and speed up your own protoyping to iteration cycle?
Simply create your free account.