Skip to main content

5 technology trends that will change enterprise software in 2018

Enterprise software used to be slow moving, legacy, safe-playing and conservative in the past. But that era is long gone with the new advancements we have seen in the last 5 to 10 years. This trend of innovation and rapid change will get accelerated during the year 2018. Here are 5 main technology areas that will change the way people build, sell and use enterprise software.
  • IaaS to PaaS to FaaS — Maintaining a server infrastructure was challenging even for very large enterprises due to the various levels of expertise needed to maintain it. But this has changed a long way with the introduction of Amazon Web Services (AWS) in 2006 and with their EC2 Infrastructure as a Service (IaaS). All the other cloud vendors followed AWS and offered their own solutions like Microsoft Azure, Google Cloud platform. Then came the next level of cloud computing frameworks, Platform as a Service or PaaS where cloud vendors provide both infrastructure as well as operating systems and a common platform to deploy and run applications developed by users. This reduces the costs within enterprises even further. Amazon and Microsoft has delivered a plethora of platform as a service capabilities through their cloud platforms. Even with PaaS frameworks, users has to run servers in the background when there are no activities from the users and this has costs them an additional amounts for no reason. This is one of the driving factors for next level of abstraction in the cloud which is Function as a Service (FaaS) or Serverless frameworks which allows users to run their applications in the cloud only when there is a user demand. That has hugely reduced the cost for the enterprise users. This trend will keep going during 2018.
  • Open source is the new standard — Proprietary, closed source, large software vendors cannot FUD open source solutions any longer. Open source software has become the defacto standard in enterprise software. With more and more people contributing to open source projects, the trust on those projects has been immensely increased within the enterprise. With millions of projects hosted in GitHub, open source projects speaks for their stability and trust within the GH through stars, issues, conversations which are public and fully transparent.
  • Containers and Microservices architectures will dig deeper — Containers are all over the place and docker has established as the major container technology. On top of docker, there are several container management software layers developed to make the life easier for application developers. Following diagram showcases the variuos technologies around containers and specifically docker.
Container technology stack
  • Artificial Intelligence and Deep Learning — The impact which AI can make into software is well understood with the usage of AI in Google and Facebook type of applications. Now it is time to make similar impact on enterprise software with introducing AI into the newly built enterprise software platforms. Deep learning is one step further than AI and it is producing far greater results with increased efficiency and better results within a shorter response times. All the big cloud vendors are investing on their infrastructure to offer enough computing power to the users through services like Google TensorFlow, IBM Watson and Microsoft Cognizant.
  • Cyber security and Data protection regulations — Within first 6 months of 2017, there has been more than 6 Billion personal records were exposed through data breaches. They cost millions of dollars to the organizations today and in the future. Trust and confidence are the most important factors in today’s business. 70% of customers reports that they would be less inclined to work with a business that suffered a public disclosure of a data breach. This is the very same reason why there are regulations such as GDPR and PSD2 coming up for protecting the user data within enterprise deployments. This will be a major trend in 2018 with the enterprise software needs to comply with these standards and regulations.
There will be some other topics which will take traction during 2018. Some of them are
  • Microservices and Service Mesh
  • Internet of Things (IOT)
  • UX in enterprise software

Comments

  1. Thanks for providing your information, keep share AWS Online Training

    ReplyDelete
  2. I admire this article for the well-researched content and excellent wording about cloud computing. It's very useful one for beginners. Nowadays cloud engineering services companies helps many organization move digital transformation. Keep share more like this.

    ReplyDelete

Post a Comment

Popular posts from this blog

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr

Understanding Threads created in WSO2 ESB

WSO2 ESB is an asynchronous high performing messaging engine which uses Java NIO technology for its internal implementations. You can find more information about the implementation details about the WSO2 ESB’s high performing http transport known as Pass-Through Transport (PTT) from the links given below. [1] http://soatutorials.blogspot.com/2015/05/understanding-wso2-esb-pass-through.html [2] http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/ From this tutorial, I am going to discuss about various threads created when you start the ESB and start processing requests with that. This would help you to troubleshoot critical ESB server issues with the usage of a thread dump. You can monitor the threads created by using a monitoring tool like Jconsole or java mission control (java 1.7.40 upwards). Given below is a list of important threads and their stack traces from an active ESB server.  PassThroughHTTPSSender ( 1 Thread )

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte