This article talks about an approach that can help customers scale large file processing workloads in AWS EKS using Kubernetes jobs and AWS step functions.
This approach uses AWS step functions to orchestrate the end-to-end flow, which involves:
This article walks through an approach to centralize log collection for lambda function with Kinesis firehose using external extensions. The provided code sample shows how to get send logs directly to kinesis firehose without sending them to AWS CloudWatch service.
Note: This is a simple example extension to help you investigate an approach to centralize the log aggregation. This example code is not production ready. Use it with your own discretion after testing thoroughly.
This sample extension:
1. Subscribes to receive
2. Runs with a main, and a helper goroutine: The main goroutine registers to
This article explains an approach to enable blue-green deployment for applications deployed in EKS. We will use existing AWS services like CodeBuild and CodePipeline to facilitate blue-green deployments for Kubernetes applications.
Do you live in a world where:
This article will talk about an approach that can help customers run integration and regression tests quicker and cheaper to improve the CI/CD process.
A month back AWS announced a preview of Lambda Extensions, a new way to easily integrate Lambda with your favorite monitoring, observability, security, and governance tools. Extensions can be published as Lambda layers, there are two types are extension:
It’s a website where people–mostly software engineers–practice their coding skills. It’s pretty similar to sites like HackerRank & Topcoder which will rank your code written for a particular problem against the ones submitted by other users
Leetcode gets primarily used for two use cases:
I never had a clear understanding when it comes to data structures and algorithms, so being a software engineer for the last 12 years, I thought it’s not a bad idea to at least start now. So as of Dec 2019, I became a…
It goes without saying when you build a native cloud application. The system should expose health check endpoints. It will enable other cloud services (like AWS Cloudwatch, Kubernetes, etc.) to monitor the health of the application continuously and trigger corresponding alerts by listening to specific metrics. In this article, let us see how to write a simple yet efficient and modular health check using spring actuator which can help you to build a highly available system
I am a big fan of leet code so when we decided to have a code challenge in our team I thought it wouldn’t be a bad idea to a build one which should include pretty basic functionalities like:
Overall it was an amazing learning experience and I am happy to walk through how I did it.
Before I start working on this I decided to come up with some guidelines so I don't over-engineer…
I would say Ehcache is the most popular and simpler framework anyone can adopt in order to implement server-side caching. It works perfectly fine if we have a single pod system. Once we move into a system which needs to be HA & autoscaling enabled then we will start running into the following problems:
Ehcache allows JMS based cache replication which would solve this issue but it involves opening up ports that may or may not be allowed in certain companies because of security restrictions.
A lot of frameworks like “Ignite”, “Redis cache”, “Hazelcast” and “Elastic…