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.
Imagine you could navigate through your data graphically directly in the web browser. Imagine you could easily equip your web application with visualisations of complex relationships. Imagine a graphical modeling tool in the web.
Microservices based architecture seems to be the common convergence point in the industry. But when it comes to security we are still struggling to evolve from monolithic systems or people oriented architecture.
The world is moving from a model where data sits at rest, waiting for people to make requests of it, to where data is constantly moving, streams of data flow to and from devices with or without human interaction. Decisions need to be made based on these streams of data in real time, models need to be updated, intelligence needs to be learned. And our old fashioned approach of CRUD REST APIs serving CRUD database calls just doesn't cut it, it's trying to fit a square peg into a round hole. It's time we moved to a stream centric view of the world.
The journey of building developer tooling has never been as exciting as it is right now. Eclipse Che is getting more and more mature, bringing collaboration and teams capabilities for developer workspaces. Theia, integrated in Eclipse Che, is providing the foundations for a modern and extensible web IDE. With the rise of cloud development platforms, we see the industry defining new server protocols, such as "Language Server Protocol" and "Debug Server Protocol" which allow to bring tooling on a wide range of platforms, such as Eclipse, Eclipse Che and VS Code.
Early Internet of Things (IoT) applications adopted cloud-centric architectures where information collected from things is processed in a cloud infrastructure and decisions are pushed back from the cloud to things. While this architectural paradigm is suitable for a subset of Consumer IoT (CIoT), it quickly shows its limitation in the context of Industrial IoT (IIoT).
Sick of the strict rules from traditional frameworks? Aspire to more freedom? Want to see some reactive code? In this talk learn to be a reactive stack Chef using the un-opinionated approach chosen by Eclipse Vert.x. Pick your language, your development model, the components from the thrilling Vert.x ecosystem, shake it and serve it hot!
Reactive Programming, Reactive eXtensions, Reactive Streams, Reactive Systems, Reactive Manifesto, that’s a lot of 'reactive' thingies. Just to make it even more confusing, 'reactive' is often associated with asynchronous, scalability, RX libraries (RX Java, RX-JS), back pressure, streams, observables, futures, promises, spreadsheets and so on…. That's a lot to digest…
Let’s clarify all these reactive thingies. This session explores the reactive landscape and explains what all these different reactives are and how they are related.
At the inception of the Eclipse Project, open source was still a young and edgy idea, accused as a pathogen by Microsoft but acclaimed as disruptive by an IBM that was facing down Microsoft and Sun. Twenty years later, it is the default for infrastructure software and the essential ingredient of IoT, Cloud and pretty much anything else apparently new in technology. We'll look back at why it worked and take some guesses about how it may influence new trends.
Cryptographic libraries are difficult to use. Various empirical studies have shown that software developers commonly struggle to correctly encrypt, sign or hash data processed within their software. Common APIs of cryptographic libraries are powerful, yet require a lot of configuration. For example, symmetric block ciphers must be configured with block modes, padding schemes, and the algorithm's key length. While the fine-grained crypto APIs allow software developers customized and flexible implementations, slight misconfigurations easily yield insecure and broken code.