darren whittingham - Fotolia
SmartBear Software, the leader in software quality tools for teams, has joined the Eclipse MicroProfile Group, an open source collaboration community for developers and vendors to optimize the development of microservices using Enterprise Java.
SmartBear has a history of supporting technology for modern application development, including the modern shift toward microservices. In 2015, SmartBear acquired Swagger and donated the Swagger Specification later that year, spawning the Open API Initiative. The Open API Initiative, operated under the Linux Foundation, governs the continued evolution of the Swagger Specification, now referred to as the Open API Specification. Later this month, the Open API Specification 3.0 is expected to be released, adding additional support for microservices.
With the Open API Specification 3.0 enabling microservice applications, SmartBear said they have a vision for making microservices production and consumption as easy as possible using Swagger tooling. The company will now also build MicroProfile solutions into its products, including SwaggerHub.
SmartBear joins a coalition of members actively involved in the MicroProfile Group, which include Red Hat, IBM, Fujitsu, Oracle, SOUJava, Hazelcast, Hammock and kumuluzEE.
NGINX releases Fabric Model on GitHub
NGINX, a provider of advanced internet infrastructure software for web application deployment and management, has announced that the Fabric Model of the NGINX Microservices Reference Architecture is now publicly available on GitHub.
Microservices expert Charles Pretzer explained in a webinar put on by NGINX that the Fabric Model is one of three architectures that NGINX has built for microservices. While other NGINX microservices models are more suited for breaking up a monolith to a more distributed, service-based architecture, Pretzer explained in a company sponsored webinar that the Fabric Model is more suited for those building new services.
"The Fabic Model is best for businesses or individuals looking to build a new application using microservices," Pretzer explained. "If you're starting from scratch, that's the best use case for Fabric Model."
Everything-as-a-service trend continues to snowball
As the "as-a-service" model evolves beyond infrastructure as a service (IaaS), platform as a service (PaaS) and software as a service (SaaS) to include new kinds of cloud-based services, the analyst firm 451 Research said there is increasing demand for managed security, managed disaster recovery, managed networking services and managed hosting. The "Voice of the Enterprise: Hosting & Cloud Managed Services" study showed that managed services and security services are attached to roughly half of the total hosting and cloud opportunity, and are increasing year-on-year, increasing their viability as part of the everything-as-a-service model.
And when they say everything, they mean it. 451 suggests vendors consider thinking outside the box and partnering with companies that can offer niche, vertical or other specialty services to increase their everything-as-a-service options.
As much of the physical infrastructure delivered through IT distribution has become invisible to end users, many businesses have put more focus on supplying new kinds of cloud services. As a result, 451 Research believes the role of the cloud services channel is now more important than ever in delivering support, maintenance and consulting services.
New to Git and distributed version control? Here are some Git examples and Jenkins-Git integration tutorials designed to help you master the popular source code versioning tool.
- The five key Git commands to master first
- Change a commit and manipulate commit history with this hard git reset example
- What happens when you git reset and push?
- Learn to undo a commit with git revert
- Use the git cherry-pick command across branches
- Change the default Git commit editor to Notepad++
- Where the Git configuration files are stored
- Make continuous integration part of your DevOps journey with this Jenkins CI tutorial
- Include Jenkins Git environment variables in your freestyle builds