Mindika Dharmabandu

  How did we approach it ? what did we consider ? When it comes to choosing a database, one of the biggest decisions is picking a relational (SQL) or non-relational (NoSQL) data structure. While both are viable options, there are certain key differences between the two that users must keep in mind when making a decision. Dimensions we looked at from the perspective of the database :  Language + Scalability + Structure +  adaption + Cost We approached it in a way so that we can understand the real complexity behind this decision, We had to think about this little differently because it involves organization and how it can be adopted, whether it is going to be cost effective, can it be scalable, Will it fit the need of the application.  There are certain instances that we found that no SQL databases that are managed databases from any cloud provider (Azure, AWS or GCP) are more expensive than traditional SQL databases. In another instant that better suited candidate is the no SQL databas

We used Google app engine and migrated close to 15 application and transformed the app landscape for the better. Google app engine truly changed the dynamics of our project and using it did really changed our lives. Speed up the development with less hurdles to jump in the infrastructure level and having the scalability built in made is easy to "Quick to Start" and "Easy to Use". Being PaaS, that is fully managed and we used inbuilt services to run our apps. Team was able to start development almost instantly after downloading the software development kit (SDK). We were able to use multiple languages to suit our need as Go, Java, PHP or Python to write an app engine application. We develop and test an app locally using the SDK containing tools for deploying apps. Every language has its own SDK and runtime. There are service-level agreement of the app engine. Any changes made to such a feature are backward-compatible and implementation of such a feature is usually st

Security, Elasticity, Scalability and Cost-Effectiveness are the primary goals of any cloud solution. We started with that idea I had to say it was a great experience. We were able to utilize the AWS service and truly develop a global solution that deliver customer satisfaction, while being presence in the region with low latency and high performance. Selecting a DB We had to solve few different problems and while implementing this Solution. first problem was that we had to overcome selecting the right data source or should I say database. While selecting the database we had to compare several different options with no SQL databases and relational databases. it is a hard choice when we go into solutioning, selecting the right database whether it is no SQL or relational databases because the implications of the cost. If you don't understand the running cost of the database you will not be able to be successful in achieving the cost effectiveness of the solution. Especially when you