Cloud has been a buzzword for almost ten years now, but still, a considerable portion of systems isn't "up there". The reasons vary from being scared through not having enough time to investigate it properly, to valid legal and/or technical reasons.
It's easy to get started and not so easy to make it right. Cloud requires serious thought and serious investment into learning the new concepts before one can understand what the trade-offs are.
We all heard of the horror stories of raking incredible fees by simply not understanding that having the infinite scaling set up creates infinite cost scaling as well.
Through many demanding migration projects, I realized there is no way I can satisfy the demand. There is simply no way to teach many organizations to bootstrap their cloud efforts right. So, I built the solution for that demand - a concentrated solution based on the verified, battle-tested configurations I made for clients throughout the years. One with proper security in place and tailored for real-world scenarios I encountered in my work.
The goal was to ease the migration, cut down the migration cost and duration, and increase the reliability and stability of the new system. But to make something like it, you first have to figure out which "templates" fit most of the use cases, and are a good fit to start extending for those cases which require more specializations.
Don't get me wrong... this isn't a sales talk, this is a talk about that journey, full of recommendations how to move to the cloud... any cloud, since the patterns and services are almost the same.
So please join to see us taking off the "mystery veil" off of the cloud, and discussing how to build your cloud native and/or hybrid cloud system without much fuss.