With the right tools, building scalable applications can be much easier than it seems. Eclipse MicroProfile allows you to build such applications easily and you get a variety of options to scale them if you add distributed data grids. These can become a backbone for building horizontally scalable services, while at the same time providing flexible caching to scale up their performance vertically.
Different types of data require different approaches of how you distribute & manipulate your data. Update frequency? Staleness? Legacy or new? Push or Pull? Check this session to see how different technologies can be applied to solve a plethora of data scenarios with different requirements.
Deploying microservices app to stg or prod is never easy but developing a microsaervice app is a true challenge. Developing such an app locally almost never replicates production environment. Is it possible to run your production Kubernetes environment in a developer mode and have IDE with all the tooling right in your browser? Eclipse Che makes it possible.
This talk will demo development of a simple micro-service application (Golang, Spring, Vue.js, node.js) in Eclipse Che, as well as talk about advantages of using web based IDEs to develop non-monolithic applications.
There's been a lot of movement in the Java EE world. From the release of its 8th edition to the shift to Eclipse Foundation and recent rebranding to Jakarta EE. At the same time Eclipse MicroProfile shown up on the EE scene with the primary goal of evolving the spec towards microservice architectures.
With all these changes happening rapidly what has happened to Arquillian, the de-facto testing tool for Java EE applications?
When the Eclipse Microprofile initiative was started in 2016, it only took about three months before version 1.0 was launched. From day one, there were four different implementations from four different vendors available.
And the progress does not stop there! Whereas version 1.0 was a subset of Java EE specifications, the following versions bring additional technologies useful for building microservices.
Current version contains APIs and implementations for:
Tracing your distributed microservices across multiple vendors and multiple servers can be difficult. After a user hits your Rest endpoint, how can you get correlated trace messages as this request goes from one service to the next, and from one server to the next, and even from one vendor to the next? And, how can these trace messages be easily collected, queried, and displayed that is useful for analysis? Several technologies need to work together to accomplish these goals. We will start with explaining the distributed tracing standard as defined by opentracing.io. Next, we will expl
“Sorry, you cannot withdraw any money, because the security service is temporarily unavailable. Kind Regards, your ATM.”
In microservice architectures, latency and system failure are added risks. How do we architect our system that it can cope well with erroneous situations and prevent the authentication service become a bottleneck? This session walks you through the concept of token based security and explains how to design a scalable and fault-tolerant security system using the Microprofile JWT-Auth with an identity and access management solution.
Eclipse Che is a browser-based IDE providing on-demand workspaces that include runtimes and IDEs. It is powered by a RESTful workspace server (with OpenShift or Kubernetes as underlying infra), plug-ins for languages, frameworks, and tools.
Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way.
But micro-services bring a lot of complexity which is maybe not always desired or needed.
Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams.
This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self Contained Systems highlighting their strengths and their weaknesses.
With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way.
First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case.