search

#microservices

Monitoring a Kubernetes-backed Microservices Architecture with Prometheus

Prometheus and Kubernetes – a match made in open-source heaven

As many startups of the last decade, SoundCloud’s architecture started as a Ruby on Rails monolith, which later had to be broken into microservices to cope with the growing size and complexity of the site. The microservices initially ran on an in-house container management and deployment platform. Recently, the company has started to migrate to Kubernetes. In their talk at the DevOpsCon, Fabian Reinartz and Björn Rabenstein demonstrated the current Prometheus setup at SoundCloud, monitoring a large-scale Kubernetes cluster.

It's not necessarily a search-and-destroy mission

Why use microservices?

Gartner projects that the worldwide public cloud services market will grow 16.5 percent by the end of this year. 451 Research found that 40 percent of companies surveyed are going to prioritize the mobilization of general business apps over the next two years. Trends like these have led developers to rapidly adopt microservices for building applications. As business needs change, forward-thinking companies are modifying, scaling and updating their apps continuously with the help of microservices.

Interview with Josh Long, Spring Developer Advocate at Pivotal

“The most important benefit of microservices is agility”

No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our fourth interviewee is Josh Long, the Spring Developer Advocate at Pivotal.

Why are microservices important for you? — Part 3

“Microservices should not be used if the organization is not embracing DevOps principles”

No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our third interviewee is Daniel Bryant, Chief Scientist at OpenCredo and speaker at the upcoming JAX London.

MicroProfile 1.0 is here

MicroProfile 1.0: HTTP is not the only way microservices communicate

MicroProfile 1.0 is intentionally feature-constrained so that a broader community can define its roadmap. The parties involved (Red Hat, IBM, TomiTribe, Payara, LJC and now SouJava) have agreed on a base set of features that defines solid and stable roots on which to grow and have added multiple member organizations and contributors. But that’s not all.

The perks of Typhoon

End-to-end latency challenges for microservices

There is pressure to define a global platform architecture and purify concepts of core business within it. Microservices is an appropriate design style to achieve this goal – it lets us evolve systems in parallel, make things look uniform, and implement stable and consistent interfaces across the system. Unfortunately, this architecture style brings additional complexity and new problems. Network latency is crucial for online businesses with a direct impact on sales.

Interview with JAX London speaker Daniël van Gils

Need a proper production platform? Docker isn’t going to solve your problem

No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our third interviewee is Daniël van Gils, a polyglot developer advocate at Cloud 66 and JAX London speaker.

Microservices checklist — Part 2

“The size of a microservice is the size of the team that is building it”

No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our second interviewee is Aviran Mordo, the head of engineering at Wix.

While you were away

#AboutLastWeek: Win some, lose some — Angular 2, Java EE 8, microservices

Each Monday we take a step back and analyze what has happened in the previous week. Last week we presented the fifth release candidate of Angular 2, we shed some light on what Java Champion Jeff Genender thinks of Java EE 8 and we launched a microservices checklist. Our first interviewee was Viktor Farcic, Senior Consultant at CloudBees. But that’s not all.

Analyzing the synergy between the performance of WSO2 MSF4J and the agility of Spring

Performance advantages WSO2 Microservices Framework for Java 2.0 brings to Spring

WSO2 Microservices Framework for Java (WSO2 MSF4J) first launched in March 2016, providing developers the ability to quickly and easily create secure, high-performance microservices in Java that support container-based deployments. WSO2 Director of Architecture, Apache member and long-time open source contributor, Afkham Azeez talks about version 2.0 of WSO2 MSF4J, which was released in late July 2016 and adds support for the widely adopted Spring application framework, among other features.

Interview with Viktor Farcic, Senior Consultant at CloudBees

Checklist: Why are microservices important for you?

No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our first interviewee is Viktor Farcic, Senior Consultant at CloudBees.

While you were away

#AboutLastWeek: Old-timers, newcomers and those in between

Each Monday we take a step back and analyze what has happened in the previous week. Last week we witnessed the birth of AngularDart, the release of IntelliJ IDEA 2016.2.1 and the reassurance that Java maintains its dominant position over other JVM languages. We learned why blockchain may outgrow Bitcoin and we discovered that microservices may not become a default architecture.