It is not an overstatement to say that building core services and exposing its APIs has become the norm in technology world. APIs abstract the functional complexity behind a very simple and easy to use interface. Today, businesses are exposing Infrastructure to Technology to Information to Storage to Anything that you can possibly imagine as a service. Continue reading APIs APIs APIs – SOA Guidelines for Internal Services
AWS Lamba is one of the very useful AWS service for performing tasks which requires more computing power like image processing. Especially if you are a startup and do not want to spend too much money upfront for reserving a high capacity EC2 instance, Lambda is your best choice. If your company has grown and if there is a need to process many images in a short duration, still Lambda comes to the rescue with its automagic demand based scaling. With AWS Lambda, scaling is no more a pain point because AWS takes care of it. Continue reading Using AWS Lambda for Image Processing
Serverless architecture is a fancy new jargon in the architecture world. There is lot of buzz around the tech community, especially with the introduction of AWS Lambda and API gateway. Of course there are lot of debates going on about what we need to consider as Serverless and not. One important thing to keep in mind is that Serverless does not mean that you run your application without any physical server. At the end of the day, your code has to run on some hardware and you cannot avoid that. It is just that whether you maintain the hardware (deployments, upgrades, scaling issues and so on) and software (in some cases) or someone else does it on your behalf. Serverless is often linked to low cost assuming the Lambda pricing, but it is not. Continue reading Serverless Architecture & its Cost
Let me first set the context by briefing about our application and its production setup. It is an internal web application used by the support team across multiple countries. The application requires session persistence without which the current work of our users will get interrupted. While persistence can be a divisive topic, any discussion for it or against it is moot in this context since we do not have a choice. I personally prefer to design nonpersistent applications, but let us not discuss about it further. We have a pool of WebLogic servers load balanced behind F5 LTM virtual server. We use LTM’s Cookie Insert method for achieving session persistence. Continue reading Our journey to F5 LTM OneConnect Profile
In this part, I will walk you through the ideas and technologies involved in creation of StickyPrint – Our Daily Standup Facilitator. If you have not read the part-1 yet, I strongly recommend you to read it first before going through this article.
There are two puzzles to solve to make it work. First we need to get sprint data from Rally and transform it to a format we want to see in our task board. Once we have the data, we need to find out a way to reliably print it in Sticky Notes. We were confident that we can solve Puzzle-1 (data retrieval and transformation) very easily in an hour or so, if we programmers can’t do it who else can. But how do we print something in Sticky Notes? No matter whatever magic we do with the data, it’s useless if not printed. So we started solving Puzzle-2 (printing) before working on Puzzle-1. Continue reading StickyPrint – Behind the Scenes
Though Agile says “it’s up to the scrum team to decide how they want to operate”, there are a few guidelines which need to be followed to reap maximum benefits out of Agile methodology. One such important guideline is the daily stand-up meeting. Our scrum teams, while transitioning from Waterfall tradition, started seeing those stand-up meetings as an additional overhead compared to the waterfall methodology. So they started complaining that there are too many meetings in Agile compared to Waterfall (a typical complaint you may hear during every transformation). Continue reading StickyPrint – Our Daily Stand-up Facilitator