2024 DevOps Lifecycle: Share your expertise on CI/CD, deployment metrics, tech debt, and more for our Feb. Trend Report (+ enter a raffle!).
Kubernetes in the Enterprise: Join our Virtual Roundtable as we dive into Kubernetes over the past year, core usages, and emerging trends.
Developer at Imixs
About
I am project lead of the open source project Imixs-Workflow and founder of the Imixs Software Solutions GmbH located in Munich/Germany. As an architect and Java EE expert I believe that an open exchange of experiences is fundamental for professional software development. twitter: @rsoika
Stats
Reputation: | 1618 |
Pageviews: | 286.0K |
Articles: | 13 |
Comments: | 43 |
Articles
Trend Reports
Kubernetes and the Enterprise
Want to know how the average Kubernetes user thinks? Wondering how modern infrastructure and application architectures interact? Interested in container orchestration trends? Look no further than DZone’s latest Trend Report, “Kubernetes and the Enterprise.” This report will explore key developments in myriad technical areas related to the omnipresent container management platform, plus expert contributor articles highlighting key research findings like scaling a microservices architecture, cluster management, deployment strategies, and much more!
Comments
Oct 23, 2023 · Marcy Tillman
Great article!
Jun 20, 2023 · Shai Almog
One thing about checked exceptions is that your code becomes much more expressive and is better understandable. I know that I am fighting a losing battle with this argument. Today, most people find it particularly cool to write short functional code without adding a single line of comment.
I think that the founders of Java really thought that expressive code would be a step forward from the then dominant C and C++ language style.
May 08, 2023 · Rahul Nagpure
This is once again the usual list of Amazon's marketing promises.
Fargate is a comparatively costly solution that makes you completely dependent on AWS. It is not difficult to run your own Kuberenetes cluster - save money and stay in control.
Sep 30, 2022 · Ralph Soika
There are a lot of tutorial like https://mkyong.com/tutorials/jsf-2-0-tutorials/
and Books : https://www.amazon.de/Definitive-Guide-Jakarta-Faces-Applications/dp/1484273095
Jan 17, 2022 · Ralph Soika
Yes, where authentication/authorization is part of jakarta EE, Microprofile provides microservice specific aspects like healthcheck, metrics, configuration, fault tolerance, tracing, openapi... of course a lot of them where inspired by spring ;-)
Jan 14, 2022 · Ralph Soika
As long as you write your code cleanly against the API and not against the implementation, this is almost not the case. At Spring, you often implement against the implementation, which can lead to problems.
Dec 09, 2021 · Micah Zayner
...or you simply use Apache Kafka - an open-source distributed event streaming platform. You can run it on your own environment and you avoid the AWS vendor lock-in....
Jul 05, 2021 · Thomas Hansen
I totally agree with you. It is incomprehensible how many companies believe that AWS or Azure are a cost-effective solution. Building your own Kubernetes cluster is not difficult, saves money, protects your data and avoids the vendor lock-in. Take a look at the Imixs-Cloud project explaining how to setup your own cluster.
Jun 24, 2021 · Vito Clover
Even if it may sound incredible. AWS does not have a monopoly on Kubernetes. You can also run Kubernetes yourself. And that's easier than you may think.
Jun 05, 2021 · Mariana Berga
Great article!
Your argument of better performance of JSON vs. XML is not always valid in my eyes.
Processing a complex JSON structure, a developer can make many faults affecting the performance. On the other hand XSLT is a high end processing technology to analyse, extract and transform even very complex XML data structure in a very fast way. It is not guaranteed that an unexperienced JSON developer can process data faster.
May 31, 2021 · Ravi Kiran Mallidi
Why did you have miss Eclipse Microprofile?
Dec 10, 2020 · Charleigh Smith
I personally don't share your view.
JSON is simply more popular than XML because it is more easy - that's a valid point.
Using XML it is possible to describe a generic value data object containing all kind of data types (not just number, text and boolean). You can map this into any other technology stack with exactly the same result of values and types. And this is simply not possible with JSON. Many APIs are satisfied with the low-expression of JSON. But there are also APIs where it is very important to distinguish between a long integer value and a float value.
Oct 05, 2020 · Sudip Sengupta
What is the reason for setting:
Sep 10, 2020 · Justin Albano
Thanks for this great article!
I had never thought about the possibilities of using Optional in Java. What is interesting is that Optional only provides a partial solution. The hint that a method returning optionals should never return null should also apply to a good API design in general, which fixes the problem of the NPE too.
May 02, 2020 · Anzhela Sychyk
Or you can stay independent and install your own Kubernetes cluster: https://github.com/imixs/imixs-cloud
Mar 16, 2020 · Saurabh Dashora
I have written an article describing how to solve the problem using the Imixs-Workflow Microservice: https://dzone.com/articles/microservices-and-business-transactions
Aug 23, 2019 · Ralph Soika
Yes, I think the global option did not work in this case.
Aug 23, 2019 · Ralph Soika
It is important that you take care of the 'node-exporter' job description in the prometheus.yml file. You need to add the service name from every node. Also you may take a look here.
Jun 21, 2019 · Jordan Baker
I like your article, but I think you have overlooked the rquirement of Business Transactions.
Business Transactions are the hidden dependencies between loosely coupled services.
I wrote this article about how to solve this kind of problem with the Microservice Saga Pattern.
Jun 12, 2019 · Arun Sharma
I like your blog that shows how easy it is to manage Docker Swarm from the console. I myself have started an open project on Github to extend the concept a bit. See https://github.com/imixs/imixs-cloud
May 30, 2019 · Michael_Gates
See also the Blog from BJ Hargrave: I am an Incrementalist: Jakarta EE and package renaming. I am hopuflly that things will be solved at the end. In my eyes Oracle's position was and still is idiotic.
May 06, 2019 · Matthieu Robin
I'm sorry, but I think you're telling again the same fairy tale about Docker Swarm compared to Kubernetes.
Kubernetes was designed for very large environments and is ideal for this. Docker Swarm offers all those who operate less than 200 containers a lightweight but highly professional solution to manage containers. See an example here.
...An Oracle Database Cluster scales much better, but that's not an argument against MySQL...
Mar 18, 2019 · Sarah Sinning
Vulnerabilities is not the cause of Open Source. Rather, Open Source ensures that such bugs can be quickly fixed. Also the download of a open source "in a second" is not the problem. In my eyes the the problem is the closed code based on open source.
Dec 19, 2018 · Dennis Byrne
I totally agree with you. For complex ajax forms I also can't see an alternative to JSF. Apart from developing a not standardized JavaScript SPA - with one of the many just-next-hype frameworks.
May 28, 2018 · Ralph Soika
DMN is a good place to model parameter-based decision trees. This article is more about complex rules for process control within a BPMN model.
May 22, 2018 · Anupam Gogoi
There is also a github-site plugin which can be used to automate the deployment process into a gihub repo. See this blog.
I agree with the authors concept. It is not wrong to store maven artefacts in github because you typically have no changes in the artifacts itself.
Mar 22, 2018 · Michael_Gates
I like your article. In my eyes, Oracle did a very bad job the last years. It was in the end a business decision. Oracle is unable to start anything with open source.
With the eclipse organization, we now have a good chance to make it a cool project again. Only then the community will grow. Yes, we need to make noise about the new Jakarta EE project...
Jan 07, 2018 · Michael_Gates
Think of the Open Container Initiative (OCI). Docker (inc.) has pushed the project in this direction. If Google and Amazon are trying to convince people to use "Kubernetes", it's your turn to decide who to follow. But Docker Swarm at its core is fine and Docker (Inc.) does a great job of maintaining the project. And not everyone needs ' Kubernetes ' see here.
Aug 24, 2017 · Duncan Brown
Maybe you can try to get a job at NASA? ;-)
Aug 23, 2017 · Duncan Brown
I also think this is really great news and it is an important step forward.
The Java EE community has grown over the years, and even though a lot of criticism has recently been made to Java EE, the community around Java EE is certainly one of the largest in the enterprise segment.
Therefore, I think that this can improve much for the future.
May 30, 2017 · Ralph Soika
Yes that's true, there is a complexity in the Java EE stack. But this complexity is well designed by the Java-Comunity-Process. So this is not a complexity that has been accidentally created. I am not against microservice architecture, but I would like to warn developers to blindly run into a generally very complex subject, just because monolithic is uncool.
I will take a look into Cloud Foundry.
Sep 22, 2016 · Sam Atkinson
I am surprised too, that MVC will be dropped. I was pleased to hear that an action-based framework will become part of the standard. But on the other hand, I can agree with the idea to push jax-rs and do more for the topics resilience and reactiveness. And client-centric JS frameworks will maybe solve the rest (which is not covered by JSF already).
Sep 14, 2016 · Ralph Soika
But you should keep in mind the following point. A growing complexity, will affect exactly the vaunted flexibility and scalability. This is not a problem of microservices, but of architecture in general. And Java EE can help you to prevent an unnecessary increase in complexity.
Sep 14, 2016 · Ralph Soika
I agree with you and that's exactly also my point of view.
Sep 13, 2016 · Ralph Soika
I totally agree with the concept of microservices. Microservices are a great idea and an important new architectural style. But when you develop a new tiny small microservice (which will maybe become more and more complex...), I think you can trust in Java EE, which will take care for your service by a reliable family of containers and proven concepts. And like Reza explained the servers do indeed start in seconds.
Sep 07, 2016 · Ralph Soika
See also the sequel: "How to Design a Business Process Service Architecture"
Aug 30, 2016 · Tim Wenger
You may also take a look at Ben.JS. It's a plain small and minimalistic JavaScript framework for single-page-applications. Take a look if other solutions seem too be to heavy for your problem.
Jun 27, 2016 · Ralph Soika
Yes you are right, each module has indeed its own workflow. However, these workflows depend also on the parent process. In my next blog I will explain how to couple services by modelling main and subprocesses. But the core idea is to keep out the process logic from the individual service layers.
May 31, 2016 · Ralph Soika
Hi David,
what I try still to understand is how you handle the state of a business object. In my case of the ordering process it is (for my understanding) necessary to store the status of the order into the order object. On the other hand, I think that any external service must validate this state, before it sends a new async event. Is this not becomming a problem when I decouple my system more and more?
May 25, 2016 · David Buschman
This all sounds like if a Java servlet container can only handle one request at one time. And if I want to handle 100 paralel users, I am forced to run 100 instances of tomcat or wildfly servers. That's not true. And the same is not true for EJB Containers or JDBC conection pooling in Java EE.
May 24, 2016 · David Buschman
David, I am not sure if I can agree with your opinion about JEE. As Tom explained it all sounds like bashing against JEE. I think we all agree that a distributed architecture in many cases can show impressive performance advantage. But I can't agree when LinkedIn, Twitter and Facebook are called for examples. There are millions of web applications out there in small to large enterprises which did not share data with the whole world. Its important that those applications act as self-contained-systems. And JEE is the perfect environment for those applications.
Mar 04, 2011 · Mr B Loid
Mar 04, 2011 · Vincent Partington