
Sergey Plastinkin
Sergey Plastinkin joined Grid Dynamics in 2007 as a Staff Software Engineer & worked with Macys, SVB, JCPenney, Neiman Marcus and the others. Great experience in Clouds, Containers, CI/CD, Big Data
Check out the latest insights

Are you currently navigating the landscape of application hosting and management with Pivotal Cloud Foundry (PCF), now known as VMware Tanzu Application Service? Perhaps you're contemplating a pivotal (pun intended) decision: the transition to cloud hyperscaler Kubernetes engines like Amazon Elas...

Of the three main cloud providers–Google Cloud Platform (GCP), Amazon Web Services (AWS), and Microsoft Azure (Azure)–GCP can definitely be considered a pioneer in terms of solutions evolution. Many of the IT products we consider to be “industry standard” today, were created or based on Googl...

Unique shopping experience portal to optimize personal assistant interactions for select customers, designed and implemented as a greenfield AWS-native solution. Our client is an American chain of luxury department stores focusing on high-end curated products and excellent customer servi...

Modern cloud providers offer compelling opportunities to modernize IT infrastructure and gain operational efficiency through cloud-native design practices, DevOps, containers and more. However, moving to the cloud isn't easy. Those who join the cloud movement soon learn that there are a lot of m...

In the previous blog post we went through the details of how to set up the Docker infrastructure with Mesos and Marathon, and how to bootstrap the environment to get it ready to host application services. Now it is time to deploy some applications. Our blog’s purpose is not only to show you a fi...

In the previous blog post we explained our overall approach to the DevOps stack used for the deployment and management of the In-Stream Processing blueprint. In this post we’ll focus on more details of Mesos and Marathon, and provide you with scripts to provision the complete computational environm...

This post is about the approach to the “DevOps” part of our In-Stream Processing blueprint — namely, deploying the platform on a dynamic cloud infrastructure, making the service available to its intended users and supporting it through the continuous lifecycle of development, testing, and roll-ou...

In the previous four blog posts in this series we covered the reference architecture of a general purpose In-Stream Processing Service blueprint. To recap, here is a list of shortcuts to the blogs in that series: … 10 reasons to migrate from PCF and embrace cloud hyperscalersRead More &...