devopsy.kinsta.cloud

Tag: Eclipse Foundation

  • Eclipse Foundation Touts Java SE Temurin Certification Momentum

    Eclipse Foundation Touts Java SE Temurin Certification Momentum

    The Eclipse Foundation revealed today the number of downloads for Java Standard Edition (SE)—dubbed Eclipse Temurin—certified using both a technology compatibility kit (TCK) and compatibility tests for evaluating associated runtimes reached 12.3 million in February.

    Tim Ellison, a project lead for creating compatibility tests for the Eclipse Foundation, said that level of activity suggests the governance framework for an Eclipse Adoptium project that enables developers to download compatible runtimes based OpenJDK source code from multiple providers is gaining traction. Members of the Adoptium working group include Alibaba Cloud, Bloomberg, Google Huawei, IBM, iJUG, Karakun AG, Microsoft, New Relic, Red Hat and Rivos. Eclipse Temurin has also become the default Java option for the GitHub Actions continuous integration/continuous delivery (CI/CD) platform.

    OpenJDK is a free and open source implementation of Java SE provided by Oracle. AdoptOpenJDK was created in 2017 to provide open source Java runtimes based on OpenJDK. Since then, AdoptOpenJDK has been downloaded more than 240 million times. The Eclipse Adoptium working group has negotiated with Oracle to create an OpenJDK Community TCK License Agreement (OCTLA) that allows it to run compatibility tests to ensure conformance to the Java specification.

    One of the reasons Eclipse Temurin is gaining traction is organizations are looking to reduce Java licensing costs during uncertain economic times by relying on an open source platform. At the same time, a consistent set of certified runtimes also reduces the level of DevOps friction that might otherwise be encountered when building and deploying Java applications, noted Ellison. There will, of course, always be multiple Java runtimes, but the level of incompatibility that would exist without testing them could be substantially higher, he noted.

    Despite the plethora of programming languages developers use, after more than 25 years, Java remains the dominant language for developers working in enterprise IT organizations. Developers may be building and deploying applications faster, but most of them will continue to rely on the programming language they already know rather than master another. In addition, many of the Java applications that have been deployed over the last two decades are now being modernized within the context of a cloud migration.

    Arguably, Java is experiencing a renaissance following efforts to make it simpler for multiple organizations to contribute code to open source projects and increase the pace of innovation. The rate at which organizations can absorb that innovation will naturally vary, but it’s clear that more organizations are now running later editions of Java that improve both performance and cybersecurity overall.

    In the meantime, DevOps teams should expect to see more Java projects moving through pipelines in the months and years ahead. While not every legacy Java application may need to be updated before being retired, it’s apparent that the bulk of Java applications are still relevant. As such, it’s probable the efforts to modernize those applications will keep DevOps teams occupied well through the end of the decade.

  • Eclipse Foundation Launches Open Source Edge Computing Initiative

    Eclipse Foundation Launches Open Source Edge Computing Initiative

    The Eclipse Foundation in collaboration with the OpenAtom Foundation today launched the Oniro project and working group to create an independent implementation of OpenHarmony, an open source operating system.

    Created by the OpenAtom Foundation, the OpenHarmony operating system is based on a HarmonyOS originally created by Huawei. It is designed to support multiple kernels but uses the Linux kernel if a device has a large amount of memory.

    It also includes a DSoftBus capability for integrating physically separate devices into a single logical super device that enables one device to control others in addition to facilitating data sharing among distributed devices.

    Huawei, in collaboration with Linaro, Seco, Array, NOITechPark and Synesthesia, has also been contributing to a continuous integration/continuous delivery (CI/CD) platform that is part of the larger Oniro project.

    Mike Milinkovich, executive director of the Eclipse Foundation, said the goal is to provide a common layer of abstraction platform that can be employed across a wide range of embedded systems that are typically being deployed at the network edge. That level of fragmentation surrounding platforms that don’t provide a lot of significant differentiated value only results in slowing down the deployment of applications, noted Milinkovich.

    As part of that effort, a dedicated working group has been created to provide a vendor-neutral structure through which contributions to the project can be made with greater transparency. The OpenAtom Foundation was created in Beijing last year with the support of Alibaba, Baidu, Huawei, Inspur, Qihoo, Tencent and China Merchants Bank. The alliance with the Eclipse Foundation brings more traditional governance rules for building open source software to the OpenHarmony project.

    In general, DevOps teams should be tracking the development of proposed de facto standards for edge computing platforms closely. More applications are now being deployed on edge computing platforms that make it possible to process and analyze data at the point where it is being created and consumed. The DevOps challenges associated with building and deploying applications across a highly distributed computing environment are considerable.

    In many cases, organizations that never really attempted or mastered continuous delivery of applications and their associated updates will be sorely challenged when it comes times to support hundreds, possibly thousands of applications, running on embedded systems based on a wide range of processors.

    In addition, many of those same DevOps teams will start to see traditional batch-oriented applications being superseded by applications based on event-driven architectures that process data in near-real-time. In most cases, those applications are going to be built on microservices-based applications that are typically more challenging to build and deploy than a traditional monolithic application.

    Arguably, IT organizations are on the cusp of a new era of IT that assumes most organizations have not only mastered DevOps best practices but are now also embracing DevSecOps best practices to secure those application environments.

    It may be a while before the open source software that will be developed by the Orino project finds its way into production environments, but it should be apparent that reducing complexity at the network edge should be a high priority for all DevOps teams heading into 2022.

  • Eclipse Foundation Creates Adoptium Working Group for OpenJDK Binaries

    Eclipse Foundation Creates Adoptium Working Group for OpenJDK Binaries

    The Eclipse Foundation announced today a working group that will establish a governance framework for an Eclipse Adoptium project that enables developers to download compatible runtimes based on OpenJDK source code.

    Members of the Adoptium working group include Alibaba Cloud, Huawei, IBM, iJUG, Karakun AG, Microsoft, New Relic and Red Hat.

    OpenJDK is a free and open-source implementation of the Java Platform, Standard Edition that is provided by Oracle. AdoptOpenJDK was created in 2017 to provide open source, high-quality Java runtimes based on OpenJDK. Since then, AdoptOpenJDK has been downloaded more than 240 million times.

    The Eclipse Foundation is now continuing that effort under an Eclipse Adoptium project that aims to become the primary source for OpenJDK-based binaries. The Eclipse Adoptium working group has negotiated with Oracle to create an OpenJDK Community TCK License Agreement (OCTLA) that will enable it to run compatibility tests to ensure conformance to the Java specification.

    Mike Milinkovich, executive director of the Eclipse Foundation, said the Adoptium WG will provide the infrastructure, marketing, community building and developer education required to ensure timely releases and adoption of Eclipse Adoptium runtimes.

    OpenJDK is a reference implementation used by multiple vendors to create their own binaries, which are only guaranteed to be compatible with the standard until the next update arrives; updates are released approximately every six months. The Eclipse Adoptium project will make it simpler for developer teams to identify which binaries are compatible with specific implementations of OpenJDK. Ultimately, the goal is to encourage developers to build applications using frameworks that make use of new OpenJDK features as they are added to the platform versus continuing to rely on older binaries.

    At the same time, however, the Eclipse Foundation is also looking at making it simpler for enterprise IT teams to rely on long term support (LTS) licensing agreements that would be based on Eclipse Adoptium runtimes, Milinkovich noted.

    Despite the plethora of programming languages developers use and even after 25 years, Java remains the dominant language for developers working in enterprise IT organizations. Over the last few years, OpenJDK has gained traction as organizations adopted an open source implementation of the specification that enabled providers of frameworks for building applications to reduce licensing costs.

    It’s not clear at what rate enterprise IT organizations are replacing proprietary editions of Java with OpenJDK. However, in the wake of the economic downturn brought on by the COVID-19 pandemic, reliance on open source software has increased to reduce costs. At the same time, many organizations are looking to build microservices-based applications using Java frameworks that are based on OpenJDK runtimes.

    Regardless of the underlying platform employed, as developers are asked to build and deploy applications faster, most of them will rely on the programming language they already know rather than take the time to master another.

  • Eclipse Foundation Formally Releases Jakarta EE 9 Spec

    Eclipse Foundation Formally Releases Jakarta EE 9 Spec

    The post-Java Enterprise Edition (EE) era has formally begun with the release of a long-awaited Jakarta EE 9 Platform and Web Profile specification from the Eclipse Foundation.

    In addition, the Eclipse Foundation has announced that version 6.0.0 of the open source Glassfish application server has now been certified to be compliant with Jakarta EE 9.

    Functionally equivalent to the existing Java EE 8 specification, the release of a Jakarta EE 9 Platform and Web Profile specification is intended to enable IT vendors that have built offerings based on Java to shift their naming conventions to Jakarta EE 9.

    Mike Milinkovich, executive director of the Eclipse Foundation, said now that the Jakarta EE 9 specification is in place IT organizations should expect to see the members of the Eclipse Foundation that contribute to the project begin working more aggressively on a Jakarta EE 10 specification that adds more features.

    Under the auspices of the Eclipse Foundation, Milinkovich added there will be a lot more focus on developing a truly cloud-native implementation of Java EE as work on the next generation of Jakarta EE platform advances.

    The rate at which new capabilities were being added to Java under the stewardship of Oracle had become an issue given the rate at which other programming languages are being advanced. Oracle agreed to relinquish control of the Java specification to the Eclipse Foundation, which in theory should lead to a faster rate of innovation as more contributors participate in an open source project.

    However, Oracle insisted on retaining the rights to the Java trademark because it has support contracts in place for existing instances of Java that provide a significant stream of revenue. Providers of rival platforms based on Java are hoping enterprise IT organizations will shift quickly to Jakarta as part of a way to reduce their support costs at a time when IT teams are under intense pressure to reduce the total cost of IT.

    Despite the rise of a wide range of programming languages in recent years, Java is still widely employed with most enterprise IT organizations, many of whom have been using Java since it was first made available by Sun Microsystems. Reliance on Java is not likely to significantly decline anytime soon; however, most IT organizations are now making greater use of additional programming languages alongside Java. In fact, many of the applications that DevOps teams are building and deploying are made up of modules that were built using different programming languages.

    It may still be a while before a Jakarta EE platform is pervasively employed in IT environments. However, it’s clear a new era that should result in advances that make it easier to deploy applications that are compatible with Java faster has arrived. How those capabilities will manifest themselves may still be unclear, but the fact that they are being worked on should be a comfort to IT organizations that have already invested millions of dollars in training developers how to build Java applications optimally.

  • Survey Surfaces Lots of Edge Computing Diversity

    Survey Surfaces Lots of Edge Computing Diversity

    A global survey of 1,652 published today by Eclipse Foundation suggests a flood is lifting all platform boats as IT organizations begin to build and deploy a wide range of edge computing applications.

    The survey finds artificial intelligence (30%) is the workload organizations plan to deploy on edge computing platforms, followed closely by control logic (29%), data exchange between multiple nodes (27%) and data aggregation and filtering (27%), also known as sensor filtering.

    The battle among providers of platforms for building and deploying these workloads is heated on all fronts. In terms of operating systems deployed, Linux (43%), FreeRTOS (35%) and Windows (31%) lead the way.

    The most widely employed developer tools are integrated development environments (IDEs) or text editors for the desktop from the Eclipse Foundation (38%) and Visual Studio Code (35%) from Microsoft. Java (20%) is the No. 1 programming language being employed at the edge and in the cloud (24%), followed by Python (17%), while C (20%) followed closely by Java (19%) is the primary language for constrained devices.

    Container images (36%), native binary (33%) and script files (30%) are the top edge computing artifacts, while MySQL/MariaDB (31%), MongoDB (22%) and PostgreSQL (21%) are the top three databases.

    IoT middleware is a tight race between Amazon Web Services (AWS) Internet of Things (35%), Microsoft Azure IoT (31%), and Google Cloud IoT Platform (30%). The top public IoT and cloud platforms are Amazon AWS (AWS), Microsoft Azure (31%) and Google Cloud Platform (26%).

    When it comes to building and deploying these applications, the top concerns are security (39%), connectivity (27%), data collection and analytics (26%), performance (24%) and privacy (23%). Communication security (43%), data encryption at rest (41%) and JSON web tokens (30%) and distributed ledgers (22%) are the most widely employed security technologies.

    In terms of communications, HTTP/HTTPS (51%), MQTT (41%) and TCP/IP (33%) are most widely employed. The dominant connectivity protocols are Wi-Fi (44%) and Ethernet (39%), with cellular and Bluetooth tied for third (37%).

    Cloud-managed over-the-air updates (48%), locally managed over-the-air updates (42%) and network cable (38%) are ranked as the top means for deploying artifacts.

    Mike Milinkovich, executive director for The Eclipse Foundation, said it appears that best DevOps processes are being extended to create an “EdgeOps” discipline around which edge computing applications are built and deployed. A wide variety of open source technologies will play a critical role in advancing EdgeOps—nearly two-thirds of respondents (65%) of respondents either experiment with, use or contribute to open source projects, with the Apache Software Foundation (51%), Eclipse IoT/Eclipse Foundation (49%), Linux Foundation (49%) and IEEE (41%) cited as being the most relevant open source bodies.

    In terms of vertical industry sectors, agriculture (26%) leads, followed by industrial automation, education, automotive and connected/smart cities all tied at 21%.

    There is, of course, multiple definitions when it comes to edge computing. However, as edge computing continues to evolve, the day when there are more workloads deployed at the edge than in the cloud or local data centers may not be all that far off. Chances are also very high that legacy approaches to managing edge computing platforms will also need to be updated to support what, by definition, are highly distributed application environments.

  • Eclipse Foundation Touts Jakarta Progress

    Eclipse Foundation Touts Jakarta Progress

    The Eclipse Foundation today published the results of survey of 2,180 software developers that finds over half of respondents (55%) have adopted Java/Jakarta EE 8.

    In addition, the Eclipse Foundation is making available an update to the Jakarta Enterprise Edition (EE) specification that will move away from the javax namespace to embrace jakarta namespaces for all components.

    Jakarta EE 8 is essentially Java EE 8, which Oracle agreed would become open source software when it transferred ownership last year to the Eclipse Foundation. The transition from Java EE to Jakarta nomenclature remains a work in process.

    The Eclipse Foundation finds the use of Java technologies is in a state of flux across the board. For example, adoption of Java 11 now stands at 28%, while Java 14 adoption is at 11%, according to the survey. That compares to 64% that are still employing Java 8.

    Spring/Spring Boot at 44% adoption continues to be the leading framework for building cloud-native applications, compared to 35% using Jakarta EE and 16% for Red Hat Quarkus, a framework that runs natively on Kubernetes.

    Usage of Eclipse Che, an open source integrated development environment (IDE) for building applications on Kubernetes, now stands at 11%, the survey also finds.

    Mike Milinkovich, executive director of the Eclipse Foundation, said it’s clear organizations are now employing multiple frameworks to build Java applications, given a 13% drop in reliance on Spring/Spring Boot from last year’s survey results.

    However, the survey also finds that overall, the use of Java to build microservice applications has declined to 39% from 43% during the same period. That drop may reflect both the complexity of building microservices-based applications, given the fact that 25% of survey respondents said they are using Java to build monolithic applications, said Milinkovich.

    At the same time, some organizations may be opting to lift and shift existing monolithic Java applications into the cloud in response to the COVID-19 pandemic, he said, noting once redeployed, those organizations may then opt to modernize those applications using microservices.

    With access to many local data centers limited during the pandemic, many organizations may have decided the most prudent option was to lift and shift Java applications as they are than re-engineer them first, he added.

    There are currently 12 frameworks officially that are compatible with Jakarta EE 8, which Milinkovich said is indicative of the continued relevance of Java technologies for building applications both inside and out of the cloud. Now that Java is available as open source software, the level of innovation surrounding Java platforms will also accelerate, he said.

    There is still a large base of developers that rely on Java and by extension Jakarta to build enterprise applications. However, IT organizations now routinely employ a wide range of programming languages and platforms to build applications. Java is still the most dominant when it comes to building backend applications; however, many organizations are still evaluating their options when it comes to building cloud-native applications on platforms such as Kubernetes.

    Java in all its forms will, of course, be around for a long time to come. The only real question is how much organizations will continue to rely on it, in an IT world that continues to transform.

  • The Eclipse Foundation Releases Eclipse Theia 1.0, a True Open Source Alternative to Visual Studio Code

    Leading open source adopters for Eclipse Theia include ARM, Arduino, EclipseSource, Ericsson, Gitpod, Google Cloud, IBM, Red Hat, SAP, and TypeFox

    OTTAWA, March 31, 2020 (GLOBE NEWSWIRE) — The Eclipse Foundation, one of the world’s largest open source foundations, today announced the release of Theia 1.0, a true open source alternative to Microsoft’s popular Visual Studio Code (VS Code) software. Eclipse Theia is an extensible platform to develop multi-language Cloud and Desktop Integrated Development Environments (IDEs) with state-of-the-art web technologies that enable developers, organizations, and vendors to create new, extensible developer experiences. Early contributors and adopters span a broad variety of industries and applications, and include companies like ARM, Arduino, EclipseSource, Ericsson, Gitpod, Google Cloud, IBM, Red Hat, SAP, and TypeFox.

    “We are thrilled to see Eclipse Theia deliver on its promise of providing a production-ready, vendor-neutral, and open source framework for creating custom and white-labeled developer products,” said Mike Milinkovich, executive director of the Eclipse Foundation. “Visual Studio Code is one of the world’s most popular development environments. Not only does Theia allow developers to install and reuse VS Code extensions, it provides an extensible and adaptable platform that can be tailored to specific use cases, which is a huge benefit for any organization that wants to deliver a modern and professional development experience. Congratulations to all the Theia committers and contributors on achieving this milestone.”

    Started as a project by Ericsson and TypeFox in 2016, the Theia project has become an integral part of enterprise cloud solutions around the world. Its momentum and distribution became significant enough that last year, the project approached the Eclipse Foundation as a potential host and vendor-neutral foundation that could further guide the project’s growth. Today, Theia is one of the Eclipse projects encompassed by the Eclipse Cloud Development Tools Working Group (ECD WG), an industry collaboration focused on delivering development tools for and in the cloud.

    The most significant differences between Eclipse Theia and VS Code are:

    • Theia’s architecture is more modular and allows for significantly more customizations
    • Theia is designed from the ground to run on both Desktop and Cloud
    • Theia is developed under the community-driven and vendor-neutral governance of the Eclipse Foundation.

    Eclipse Theia is designed to work as a native desktop application as well as in the context of a browser and a remote server. To support both situations with a single source, Theia runs in two separate processes. Those processes are called frontend and backend respectively, and they communicate through JSON-RPC messages over WebSockets or REST APIs over HTTP. In the case of Electron, the backend, as well as the frontend, run locally, while in a remote context the backend would run on a remote host.

    Both the frontend and backend processes have their dependency injection (DI) container to which extensions can contribute. Similar to VS Code’s online marketplace for code extensions, Eclipse Theia 1.0 also has a marketplace that is available today and, in the spirit of true open source community, allows for even non-VS Code applications to use these extensions.

    The Eclipse Foundation has a proven track record of enabling developer-focused open source software collaboration and innovation earned over more than 15 years. Home to critical cloud native open source projects, including Jakarta EE, Eclipse Che, and more, the Foundation’s more than 375 collaborative projects have resulted in over 195 million lines of code — a $10 billion shared investment.

    To get involved with the Eclipse Theia Project and begin contributing, please visit https://theia-ide.org/.

    For more information about the Eclipse Cloud Development Tools Working Group, view the Charter and ECD Working Group Participation Agreement (WPGA), or email membership@eclipse.org. You can also join the ECD Tools mailing list.

    Quotes from Eclipse Theia Project Adopters and Contributors

    Arduino
    “As one of the world’s largest open source ecosystems for hardware and software, we fully support extending vendor-neutral governance to every aspect of software development,” said Luca Cipriani, CTO of Arduino. “Eclipse Theia is another important step in that direction. Our community has been eagerly advocating for functionality for some time.”

    EclipseSource
    “We actively support an increasing number of customers in adopting Eclipse Theia and in migrating their existing tool chains to the cloud,” said Dr. Jonas Helming, principal software architect and general manager of EclipseSource. “The 1.0 release formally reflects what is already a fact; Theia is a mature, stable, and powerful platform for building cloud-based IDEs and tools.”

    Ericsson 
    “Eclipse Theia is an extensible open source platform for creating and maintaining custom IDE and IDE-like applications. A huge benefit of Theia is that it allows developers to start with a desktop application and easily transition it to run in the cloud without having to rewrite it,” said Gunnar Nilsson, Ericsson’s open source strategist. “Having a truly open source solution is why we helped to start this project more than three years ago. We’re very pleased that the Eclipse Foundation has helped us guide this first official release and look forward to many more in the years to come.”

    Gitpod
    “As one of the creators for the Eclipse Theia project, this first official release is the realization of years of work from a fantastic community,” said Sven Efftinge, co-founder of both Gitpod and TypeFox and current CEO of Gitpod. “Finally we have a true open source alternative for desktop and cloud IDEs that rivals the best the industry has to offer. We firmly believe this is just the beginning for Eclipse Theia.”

    Red Hat
    “At Red Hat we believe that developer teams need great tools to succeed in the new open hybrid cloud world,” said Thomas Mäder, Red Hat’s principal software engineer and committer to the Theia project. “Eclipse Che is one of the fastest growing open source cloud IDEs and for version 7, we replaced our own IDE code with Eclipse Theia. The results have been great. We have a more modern IDE that is compatible with Visual Studio Code extensions and a vibrant, vendor-neutral community. Red Hat sees a lot of potential in Eclipse Theia and is committed to grow the editor as part of the community.”

    SAP
    “SAP has been providing cloud-based development tools based on Eclipse open source projects since 2014,” said Michael Wintergerst, SVP, SAP Cloud Platform Core at SAP. “SAP Business Application Studio, based on Eclipse Theia 1.0, provides our customers with an efficient business application development environment for their Intelligent Enterprise for both public and private cloud. We see our customers benefiting from the rich set of add-on tools that will be available in the free, vendor-neutral extensions marketplace.”

    About the Eclipse Foundation
    The Eclipse Foundation provides our global community of individuals and organizations with a mature, scalable, and commercially focused environment for open source software collaboration and innovation. The Foundation is home to the Eclipse IDE, Jakarta EE, and over 375 open source projects, including runtimes, tools, and frameworks for a wide range of technology domains such as IoT, edge computing, automotive, geospatial, systems engineering, and many others. The Eclipse Foundation is a not-for-profit organization supported by over 300 members, including industry leaders who value open source as a key enabler for business strategy. To learn more, follow us on Twitter @EclipseFdn, LinkedIn, or visit eclipse.org.

    Third-party trademarks mentioned are the property of their respective owners.