Tuesday 22nd March, 2016
10:40am to 11:10am
In the current technical world, SaaS providers have plenty to help them out: from public clouds, to containers. From microservices architectures, to limitless scaling potential. But when you need to deploy multiple singe-tenant applications that use these, how do you manage to share resources while keeping sensitive data apart? In this presentation I'll talk about how we did it at ironSource.
In this talk I’ll focus on how we quickly discovered growing pains when scaling up a single-tenant SaaS to multiple customers at ironSource.
On the one hand we wanted to make use of shared resources (be it code, containers or physical resources) as much as possible; on the other hand, we promised customers a single-tenant application, and so needed to segregate sensitive data.
We needed a solution that would allow us segregated data, across multiple datacenters while remaining cost-conscious regarding resource usage. And, of course, the system would need to be balanced between self-managing itself and requiring manual intervention for unlocking secure data.
In the end we built a mashup of segregated secure data stores on (as much as possible) shared architecture at AWS using some great emerging (and some more time tested) open source technologies, including Chef, Consul and Vault.
Principal Architect, IronSource
11:10am How to Migrate Your Application to Micro-Services Using Docker and Codefresh by Raziel Tabib and Oleg Verhovsky
Sign in to add slides, notes or videos to this session