Sophia Kokkoni has over 20 years of experience as an Oracle application/database server administrator and computer programmer. She has extensive experience installing, configuring, and maintaining Oracle databases, application servers, and business intelligence software. She also has experience developing applications using tools like Oracle Forms & Reports, PowerBuilder, and Discoverer Reports.
Transaction Control – a Functional Approach to Modular Transaction Management...mfrancis
OSGi Community Event 2016 Presentation by Tim Ward (Paremus)
Transactions are a critical part of almost all Enterprise applications, but correctly managing those transactions isn’t always easy. This is particularly true in a dynamic, modular world where you need to be certain that everything is ready before you begin.
With the advent of lambda expressions and functional interfaces we now have new, better tools for defining transactional work. The OSGi Transaction Control service uses these functional programming techniques to scope transactions and resource access, providing control and flexibility while leaving business logic uncluttered. The resulting solution is decoupled, modular and requires no container magic at all, making testing and portability a breeze.
Background
Software controlled transactions have existed for a long time — commercial products that are still available now can trace their origins back to the 1960s. Since that time a lot has changed, first we saw the rise of C, then of Object Oriented programming, then of the Web, and now of Microservices.
Over the same time period there have been significant changes to the way that transactions are managed – either transaction boundaries have to be explicitly declared, or the management role is delegated to a container technology. Given the complexity of correctly managing the transaction lifecycle, container managed solutions are regarded as the gold standard, however container managed solutions introduce their own problems.
The rise of the Spring framework was a reaction to the complexity, and heavy-touch management of the original Java EE specifications. Instead Spring focussed on “pure POJO” programming, designed to make your code easily portable, runnable and testable inside or outside the container.
While Spring did a much better job of hiding complexity than those early Java EE servers, the fundamental problem with any pure declarative approach is that there must be a container somewhere. Without a container there is no code to start or end the transaction. Even now with Spring, EJB 3.2, CDI etc, the promise of simpler, container independent components is an illusion.
The big problem with declarative transaction management is that it tries to take away too much from the application code, replacing it with “container magic”. The problem with relying on magic is that the resulting system ends up being more complex, not less. We therefore should be aiming to simplify and minimise transaction management code, not eliminate it entirely. Java’s support for functional techniques opens a whole new set of API possibilities for transaction management, and the Apache Aries project has been exploring the possibilities of providing generic resource and transaction management in a concise, type-safe way. Examples from this project demonstrate how transaction management can be made both simple and explicit at the same time.
Transaction Control – a Functional Approach to Modular Transaction Management...mfrancis
OSGi Community Event 2016 Presentation by Tim Ward (Paremus)
Transactions are a critical part of almost all Enterprise applications, but correctly managing those transactions isn’t always easy. This is particularly true in a dynamic, modular world where you need to be certain that everything is ready before you begin.
With the advent of lambda expressions and functional interfaces we now have new, better tools for defining transactional work. The OSGi Transaction Control service uses these functional programming techniques to scope transactions and resource access, providing control and flexibility while leaving business logic uncluttered. The resulting solution is decoupled, modular and requires no container magic at all, making testing and portability a breeze.
Background
Software controlled transactions have existed for a long time — commercial products that are still available now can trace their origins back to the 1960s. Since that time a lot has changed, first we saw the rise of C, then of Object Oriented programming, then of the Web, and now of Microservices.
Over the same time period there have been significant changes to the way that transactions are managed – either transaction boundaries have to be explicitly declared, or the management role is delegated to a container technology. Given the complexity of correctly managing the transaction lifecycle, container managed solutions are regarded as the gold standard, however container managed solutions introduce their own problems.
The rise of the Spring framework was a reaction to the complexity, and heavy-touch management of the original Java EE specifications. Instead Spring focussed on “pure POJO” programming, designed to make your code easily portable, runnable and testable inside or outside the container.
While Spring did a much better job of hiding complexity than those early Java EE servers, the fundamental problem with any pure declarative approach is that there must be a container somewhere. Without a container there is no code to start or end the transaction. Even now with Spring, EJB 3.2, CDI etc, the promise of simpler, container independent components is an illusion.
The big problem with declarative transaction management is that it tries to take away too much from the application code, replacing it with “container magic”. The problem with relying on magic is that the resulting system ends up being more complex, not less. We therefore should be aiming to simplify and minimise transaction management code, not eliminate it entirely. Java’s support for functional techniques opens a whole new set of API possibilities for transaction management, and the Apache Aries project has been exploring the possibilities of providing generic resource and transaction management in a concise, type-safe way. Examples from this project demonstrate how transaction management can be made both simple and explicit at the same time.
OSGi for European and Japanese smart cities - experiences and lessons learnt ...mfrancis
OSGi Community Event 2016 Presentation by Levent Gurgen (CEA)
Internet of Things (IoT) is the digital skin of the physical world. It has specific requirements such as dynamicity to self-adapt to the continuously changing physical context. The world is heterogeneous and the objects should interoperate to collaborate, thus interoperability is essential. Openness and short learning curve are other requirements so that innovators (e.g. startups) can rapidly build applications with reduced time-to-market and avoid vendor lock-in. Reuse of software and hardware is also particularly important since billion of devices are expected to be deployed in the coming decades and those devices should be multi-purpose and reusable by applications from different domains and not be specific to a given domain.
OSGi has – since 15 years ago – the answers to those requirements of today’s IoT. Its powerful run-time environment for the dynamicity, its service-oriented approach hiding heterogeneity, its modularity making the reuse extremely simple, and last but not least, its open approach giving the potential to democratize the IoT.
The talk will illustrate the benefits of OSGi for IoT with concrete deployed examples, in particular in smart city domain in Europe and Japan via the collaborative projects such as ClouT and FESTIVAL.
[ Co-Fondateur | Villa HOH | Business Dev & Projets Technologiques & Opérations IT] Alain Azonlignon Est un passionné et pratiquant des nouvelles technologies qui intervient en tant que Consultant Senior ICT auprès de diverses entreprises en Europe et en Afrique. Sa vision au sein de la #VHOH se résume dans la citation : "Mes modèles en affaires sont les Beatles. Ils sont quatre gars qui compensent les défauts des uns et des autres. C'est ainsi que je vois le business : de grandes affaires n'ont jamais été réalisées par une seule personne ; elles sont réalisées par une équipe de gens" (Steve Jobs). #Entrepreneuriat #Motivation #Opportunité #Transformation #Digital #Digitalisation #Digital_Academy #Jeunes #Entrepreneurs #Villa_HOH #VHOH #HOH #Innover #Expérimenter #Partager #NWOT
OSGi for European and Japanese smart cities - experiences and lessons learnt ...mfrancis
OSGi Community Event 2016 Presentation by Levent Gurgen (CEA)
Internet of Things (IoT) is the digital skin of the physical world. It has specific requirements such as dynamicity to self-adapt to the continuously changing physical context. The world is heterogeneous and the objects should interoperate to collaborate, thus interoperability is essential. Openness and short learning curve are other requirements so that innovators (e.g. startups) can rapidly build applications with reduced time-to-market and avoid vendor lock-in. Reuse of software and hardware is also particularly important since billion of devices are expected to be deployed in the coming decades and those devices should be multi-purpose and reusable by applications from different domains and not be specific to a given domain.
OSGi has – since 15 years ago – the answers to those requirements of today’s IoT. Its powerful run-time environment for the dynamicity, its service-oriented approach hiding heterogeneity, its modularity making the reuse extremely simple, and last but not least, its open approach giving the potential to democratize the IoT.
The talk will illustrate the benefits of OSGi for IoT with concrete deployed examples, in particular in smart city domain in Europe and Japan via the collaborative projects such as ClouT and FESTIVAL.
[ Co-Fondateur | Villa HOH | Business Dev & Projets Technologiques & Opérations IT] Alain Azonlignon Est un passionné et pratiquant des nouvelles technologies qui intervient en tant que Consultant Senior ICT auprès de diverses entreprises en Europe et en Afrique. Sa vision au sein de la #VHOH se résume dans la citation : "Mes modèles en affaires sont les Beatles. Ils sont quatre gars qui compensent les défauts des uns et des autres. C'est ainsi que je vois le business : de grandes affaires n'ont jamais été réalisées par une seule personne ; elles sont réalisées par une équipe de gens" (Steve Jobs). #Entrepreneuriat #Motivation #Opportunité #Transformation #Digital #Digitalisation #Digital_Academy #Jeunes #Entrepreneurs #Villa_HOH #VHOH #HOH #Innover #Expérimenter #Partager #NWOT