When trying to gain more knowledge about microservices, it’s nearly impossible to get around all the aspects of DevOps. The improvement of the DevOps processes is one of the major advantages for following the microservices philosophy. To get a better understanding about what DevOps really means (and what not), I’d like to collect some information here.
I wrote an article on another blog – brewcloud, the blog about our team’s project from SAP’s IoT-challenge … check it out!
I would like to use the IoT-challenge and the brewcloud-project as opportunity for getting in touch with iOS-app-development in general (I mentioned my first steps in my last article) and the SAP Cloud Platform SDK for iOS in special.
When digging deeper into this topic, it seems first important to understand what SAP Fiori really is. Obviously, it has something to do with new, modern, mobile-enabled UIs by SAP, but is it a development language, a framework? What’s the exact definition of SAP Fiori? Is it the same as SAPUI5?
View original post 538 more words
Ok, I think after writing the last article, I generally understood: The usage of Microservices is good because it makes your IT landscape very flexible. Changing them is easy, testing them is easy, redeploying them takes in best case seconds. If you use them successfully, this advantages help you to deliver new features quickly to your users which nowadays is key in the competition.
When reading further articles about the topic, I found some interesting reports about big tech companies using microservices productively. That’s pretty interesting because reading theoretical books is one thing, but gaining insights and experience reports of real usage is another level of information.
One prominent early adopter of the microservices-approach is Netflix. Originally, this article was supposed to cover several copanies and their IT philosophies. But Netflix has is too interesting to write less than one article about it. Continue reading “Netflix’s army of monkeys”
So the first thing I would like to dig deeper into are microservices.
As I am in touch with some common IT- and tech-magazines and -blogs, I stumbled over that topic again and again, but I never really understood what this hype was all about. Anyhow, it seems that you can’t get around microservices, so I’d like to collect what I figured out about microservices. ( I think one of the earliest famous articles was the one by Martin Fowler: click )
The problem which microservices want to adress is that quite often, the programs in enterprise IT-landscapes are put in one big application. Actually, I have also seen this or some aspects of it in one of the systems I worked with for a long time. Continue reading “microservices – motivation”
(I will write some texts about tech topics and I will write them in English. First, that’s kind of common in the tech world and second, it’s easier to connect with people around the globe if the text is in English.)
Soon, I will change my job and work in a new role within SAP. I will support customers with the SAP Cloud Platform , SAP’s Platform-as-a-Service-offer. One of the most common reasons for using a PaaS is enabling a development environment that is easy to set up and supports you in deploying and running your applications afterwards.
That brings me back to the world of non-SAP-software-development where I have some roots due to my Java history, but I haven’t touched that world too much in the lost couple of years working as SAP-consultant: Continue reading “back in the free world”
Eben habe ich mal meinen letzten Beitrag über “mein 2017” gelesen. Da geht es unter anderem über Dinge, die mich an meinem Beruf interessieren: Cloud, IoT, “Innovationsthemen” (ein wahnsinnig inflationär benutzter Begriff)
Ich muss sagen: Davon habe ich erstaunlicherweise wirklich viel erreicht. Ab August werde ich mich in einem neuen Job – eine Rolle zwischen Vertrieb und Beratung – um die SAP Cloud Platform kümmern. Das ist das PaaS-Angebot der SAP, das Kunden einen schnellen und unkomplizierten Einstieg in die Welt der Cloud-Angebote bietet.
Offiziell nenne ich mich dann “SAP Cloud Platform Customer Engagement Executive”.
Außerdem darf ich mich aktuell noch zwei mega spannenden Nebenschauplätzen widmen. Continue reading “nicobost 1.1”