Into the Cloud

I started my career with CRM industry in 2007. 10 years have passed since then. And look how everything has changed! It’s not only Siebel CRM to SFDC or only a change in a CRM platform. It’s not only move from waterfall to agile. There is more to it.

Siebel CRM was a revolutionary product in itself. And so as others at that time. Oracle, SAP, these companies started to come up with Products, rather than only services. Now there was no need to start coding from scratch to build your CRM or ERP platform. Only customisations to these ready made products were needed. These products were spread across various horizontals and verticals, making them almost ready to use for any industry. No need to write thousands of lines of code! These technologies proved cutting edge technologies in those times.

And then Cloud walked in. Companies spent a lot of money, time in managing the infrastructure. With cloud, this burden was taken off IT. Now you have freedom to utilise these efforts in more meaningful research and functionalities development. Cloud acted as a catalyst for machine learning and AI to pick up so fast. Machine learning algorithms, especially deep learning ones where there are multiple levels, often results in heavy computations. When infrastructure is on cloud, there was no need to worry about it anymore. Processing power, storage power was all available on demand. Research and development in software world was never easier and faster than this. 

Cloud infrastructure has changed the face of IT. AWS, Azure , Google and many other cloud platform and service providers are all ready to transform the software development world. In fact, it’s already changed. It’s not only evolution of technology, it’s a change in the way of working. The way of doing businesses is changed altogether. The gap between business and IT is closing day by day. Becoming digital, data driven business is the goal for all the businesses today.

What’s stopping you then? Let’s fly! Sky is the limit!


Comments

Post a Comment

Popular posts from this blog

Understanding Wide-Column Stores

To understand the concept  more clearly, let’s start with an example of  Relational database : Customers Id Product FN Date Country 1 Dell Harry 17/04/2018 India 2 Dell Harry 17/04/2018 India 3 Apple Ron 17/04/2018 India 4 Sony Ron 17/04/2018 South Africa 5 Sony Hermione 17/04/2018 South Africa When we convert this to a  Column Store , this is how it looks like: FN LN Product Date Country Id Value Id Value Id Value Id Value Id Value 1-2 Harry 1-2 Potter 1-2 Dell 1-5 17/04/2018 1-3 India 3-4 Ron 3-4 Weasley 3 Apple 4-5 South Africa 5 Hermione 5 Granger 4-5 Sony Now a  Wide Column store  will Group the columns which are accessed frequently together into one , like Id Name 1-2 FN Harry LN Potter 3-4 FN Ron LN Weasley 5 FN Hermione LN Granger Some key points are, Columns
Read more

Two pizza team!

Image
Came across this terminology while reading about APIs based on microservices architecture. So, what are two pizza teams? Yes, they are small enough to be fed by 2 large pizzas! But how are they related to microservices?! We will find out. Amazon, being a popular online store, wanted to be able to innovate in IT space quickly. But their monolith architecture was not allowing them to make software changes quickly. Monolith architectures are the old school enterprise architectures where all the components of the software are tightly coupled. These APIs are powerful and perform lot of disparate functions. Even a small change in such systems needs a lot of planning, impact analysis, availability from other teams. This definitely slows down the software release cycle. Typically in such environments there are different teams like test team, deployment team, UI team, backend development team etc who work in silos. Any small or big change goes through a long process of build, test, deploy
Read more

Relational and Non-relational databases

In old days, when we used to think of 'database', we would only picture tables and columns, primary and foreign keys, complex joins, intersection tables etc. We often use ER diagrams, relationships to design and define such models. These databases are widely used and are stable. They adhere to  ACID  principles, provide  immediate consistency  which are most important when it comes to transaction handling. The most widely used products are  Oracle, Teradata, SAP Hana, IBM db2, MySQL, Amazon Aurora, Maria db (comes by default on linux distributions), postgreSQL . Then why is there a need of non-relational database? The reason is Data itself. Data is now considered most valuable resource, even more than Oil!! No wonder that social networking site like Facebook and twitter actually run the world. They decide the trends, what people read, what they think. All from the power of Data. Anyways that’s a topic for another post. Data from web, genomics data, data from IoT devices
Read more