<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1919858758278392&amp;ev=PageView&amp;noscript=1">

Bahubali Shetti

Bahubali Shetti

Bahubali Shetti

VMware

Bahubali leads a team of Public Cloud Advocates at VMware focused entirely on best practices of application development, deployment on AWS/Azure/GCP. Check out https://cloudjourney.io. Bahubali has held previous roles as developer, product manager, sales engineer, and even Venture Capitalist. He's been working on various topics and capabilities on Cloud for the last 10 years.

Session: Creating a stateful application with K8S and AWS DB Services (Document DB/ElasticCache)

When creating applications in Kubernetes where do you keep the data? Conventional wisdom suggests - in another container on the K8S cluster. 

However, are you willing to manually scale and manage the DB portion of your application. Most likely you're NOT a DB admin. 

The alternative? Use a services like AWS Document DB and AWS ElasticCache. These provide provide scale, security, and availability with minimal administration.

This session will walk through a simple e-commerce application with services like Cart and Order that require Redis and MongoDB respectively.

In particular I will walk through
1) The pitfalls of using a container based implementation of Redis and MongoDB in the application (walk through the complexities of scaling these)

2) How to properly configure and connect AWS Document DB (alternative to MongoDB) and AWS ElasticCache (alternative for Redis) with the appropriate services (order and cart)
a-AWS ElasticCache configured and connected to a Cart service (running on K8S and written in Python)
b-AWS DocumentDB configured and connected to an Order service (running on K8S and written in Python)

In the end - ANY hyperscaler DB service (AWS/GCP/Azure based) should be used as the prime location for your data.