What Are Microservices?
Microservices are one of the latest trends in software design where multiple independent services communicate among themselves and have their own processes and resources. This approach differs from a typical client-server application design. The usual client-server application consists of one or more clients, a monolithic back-end which includes all domain data and logic, and an API which allows clients to access the back-end and its functionality.
In a microservices architecture, the described monolithic backend is instead substituted by a suite of distributed services. This design allows better separation of responsibilities, easier maintenance, greater flexibility in the choice of technologies for each service, and easier scalability and fault tolerance. At the same time, complex distributed systems have their set of challenges. They have a greater chance of having to deal with race conditions, and they are harder to debug as problems are not easily pinpointed to one single service, but are instead distributed through many. If an effort is not made to follow the best practices while building such a system, you may find yourself surrounded by fires that you do not know how to put out. Special care must be taken with the services’ payload contracts, as changes in one service may affect all its clients, and consequently all the back-end’s service suite. (more…)
With the advent of tools like Docker, Linux Containers, and others, it has become super easy to isolate Linux processes into their own little system environments. This makes it possible to run a whole range of applications on a single real Linux machine and ensure no two of them can interfere with each other, without having to resort to using virtual machines. These tools have been a huge boon to PaaS providers. But what exactly happens under the hood?
These tools rely on a number of features and components of the Linux kernel. Some of these features were introduced fairly recently, while others still require you to patch the kernel itself. But one of the key components, using Linux namespaces, has been a feature of Linux since version 2.6.24 was released in 2008.
Anyone familiar with
chroot already has a basic idea of what Linux namespaces can do and how to use namespace generally. Just as
chroot allows processes to see any arbitrary directory as the root of the system (independent of the rest of the processes), Linux namespaces allow other aspects of the operating system to be independently modified as well. This includes the process tree, networking interfaces, mount points, inter-process communication resources and more.
Why Use Namespaces for Process Isolation?
This videos will show you on how to install SAP HANA platform edition and will be continue with installation of SAP NetWeaver 7.4 on it.
There are some tricky part for installation of this SAP NetWeaver on HANA. You have to use xfs file system for data filesystem (on directory :/hana/shared). On this tutorial video, I use xfs for whole root (/) directory.
Installation of SAP HANA platform edition.
Preparation check of SAP NetWeaver 7.4.
Installation of SAP NetWeaver 7.4 part 1.
Installation of SAP NetWeaver 7.4 part 2 (final part).
Enjoy it, guys !!
All questions could be sent to my email : email@example.com
This video show you on step by step installation of SAP NetWeaver 7.4 using Oracle 12c as database server on SuSE Linux Enterprise Server 11 SP 4.
Installation part 1 :
Installation part 2 :
Installation part 3 :
Installation part 4 :
Lately I have upload some video on how to install SAP NetWeaver 7.4. I am using DB2 10.5 FP 3 as database server and using SuSE Linux Enterprise Server 11 SP 4.
Preparation check before installation.
This video show you on how to apply SAP HANA license key which you have been ask from http://support.sap.com/licensekeys. Applying license key through SAP HANA Studio.
This video show you on how to install SAP HANA Studio on SuSE Linux Enterprise Server 11 SP 4. We can use SAP HANA Studio to access, manage, and maintain SAP HANA database server.