Categories
54cuatro-EN

Some loose ideas about containers

It is not new that the containers are already an industry standard, enable agile developments, improve time to market, improve #analytics and generate a quickly verifiable ROI.

We are in a #HYPE moment of the #Microservices era. And we see a lot of adoption of this architecture but there is a long way to go, and there are still many who could not make any progress in this regard and we are already talking about #ServiceMesh, a new component that facilitates communication.

But what is Service Mesh?

Service Mesh is a layer that improves the format in which applications built on Microservices communicate with each other. Previously in #Monolithic or #SOA developments, calls were made within each application or between layers. But in the new scheme, calls are replaced by calls made via #API communications.

This has significant advantages, as it allows developers to focus on business logic and not have to work on the communications layer. But there is a lack of standardization of API communication, as there is no defined protocol for API creation.

This is when Service Mesh becomes important. Why?

Because it is a mesh of services that stands above microservices, being a low latency communications solution that gives us discovery for new services, and with it the possibility to create rules of load balancer, authentication, encryption, among other things , and also allowing us to have monitoring to ensure the availability of our APIs.

There are many Service Mesh on the market such as #Istio or #Envoy, and from #OpenShift version 4 there is the OSMO (Openshift Service Mesh Operator) which enables the possibility of better tracking, routing and optimization of application communication.openshift y service mesh

If you need to modernize the architecture write or call me, so we can determine the level of maturity if your company to adopt microservices, the level of practice Agile / DevOps and with an assessment we can accompany you to the next level.

Posted by our Sales Director, Rodrigo Yañez in https://www.linkedin.com/pulse/algunas-ideas-sueltas-sobre-containers-microservicios-rodrigo-ya%C3%B1ez/

Get in touch

Categories
54cuatro-EN

It is the time of DataOps. Know the details

DataOps, is a methodology that emerged from Agile cultures that seeks to cultivate data management practices and processes to improve the speed and accuracy of the analysis, including access, quality, automation, integration and data models.

DataOps is about aligning the way you manage your data with the goals you have for that data.

It is not bad to remember part of the Manifiesto DataOps:

  1. People and interactions instead of processes and tools
  2. Efficient analytics solutions instead of comprehensive documentation
  3. Collaboration with the consumer instead of contractual negotiations
  4. Experimentation, interaction and feedback instead of direct extensive design
  5. Multidisciplinary ownership of operations instead of isolated responsibilities.

We are going to give a clear example of #DataOps applied to the reduction of the customer #turnover rate. You can take advantage of your customers’ data to create a recommendation engine that shows products that are relevant to your customers, which would keep them buying for longer. But that is only possible if your data science team has access to the data they need to build that system and the tools to implement it, and can integrate it with your website, continuously feed new data, monitor performance, etc. For that you need a continuous process that will require you to include information from your engineering, IT and business teams.

In order to implement solutions that add value, it is necessary to manage healthy data. Better data management leads to better data, and more available. More and better data lead to a better analysis, which translates into better knowledge, business strategies and greater profitability.

DataOps strives to foster collaboration between data scientists, engineers and IT experts so that each team works synchronized to leverage data in the most appropriate way and in less time.

DataOps is one of the many methodologies born from #DevOps. The success of DevOps lies in eliminating the silos of traditional IT: one that manages development work and another that performs operational work. In a DevOps configuration, software implementation is fast and continuous because all the equipment is linked to detect and correct problems as they occur.
dataops

DataOps is based on this idea, but applying it throughout the data life cycle. Consequently, DevOps concepts such as CI / CD are now being applied to the data science production process. Data science teams are taking advantage of software version control solutions such as GitHub to track code changes and container technology such as Kubernetes and Openshift to create environments for Analysis and deployment of models. This type of data science and DevOps approach is sometimes called “continuous analysis.”

However. So far the whole theory. But … How do I start implementing DataOps?

This is where you should start:

  • #Democratize your data. Remove bureaucratic barriers that prevent access to the organization’s data, any company that strives to be at the forefront needs data sets that are available.
  • Take advantage of #opensource platforms and tools. Platforms for data movement, orchestration, integration, performance and more.
  • Part of being agile is not wasting time building things that you don’t have to do or reinvent the wheel when the tools your team already knows are open source. Consider your data needs and select your technology stack accordingly.
  • Automate, automate, automate. This comes directly from the world of DevOps, it is essential that you #automate the steps that unnecessarily require a great manual effort, such as quality control tests and data analysis pipeline monitoring.
  • Enable self-sufficiency with #microservices. For example, giving your data scientists the ability to implement models such as #APIs means that engineers can integrate that code where necessary without #refactoring, resulting in productivity improvements.
If you want to know more, we recommend entering our Linkedin group, DataOps en Español.
Get in touch

    Por favor, demuestra que eres humano mediante la selección el camión.