As Container Solutions grows, so does the number of projects we commit to every year. To keep quality high and continue to serve our clients well, we have learned to streamline the way we deliver our services.
Engineers at Container Solutions take on complicated and creative projects and might become lost along the way. To create something great, you have to become part of it. You have to live and breathe it. But that passion can also become a problem, because it’s too easy to lose sight of what is essential.
I’d like to share with you the architecture and programming pattern we've been using to build Cloud Native applications. The use case I'm going to present is a RESTful application deployed on AWS, using AWS API Gateway and AWS Lambda. I want to show how by adopting specific AWS components and programming paradigms, we can increase the reliability of the applications we write, while also improving their maintainability.
You may be wondering, what is the relationship between high-performance organisations and Cloud Native? It’s quite simple, really. Cloud Native is a sociotechnology, meaning it encompasses technical elements, like containers and Kubernetes, social elements, like strategic leadership, and sociotechnology elements, such as microservices.
Container Solutions is a consulting company that focuses on Cloud Native transformations. Working as a Cloud Native engineer here means you get assigned to work on projects for particular clients. When you finish one project, you are moved to the next one.