- Artykuły z tagiem microservices

Microservices are still pretty popular in our industry since they imply lots of benefits. However working with that kind of architecture might be annoying when it comes to commit the changes using GIT. Why? Simply because in a common approach, each microservice should be put in a separate repository. Therefore, instead of doing your typical „GIT sequence” once, you end up with few terminals where you do pretty much the same job. Fortunately, you can avoid that with no big deal. ...

Dziel się z innymi:
Working with microservices and GIT - Forever F[r]ame

Narzędzia 1019 dni, 6 godzin, 25 minut temu dpawlukiewicz 132 źrodło rozwiń

Today’s post is going to shortly discuss entire architecture,  I’m going to implement in next three months. Since I’m not microservices master, some of my current decisions might be stupid or just not efficient. I so, please let me know in the comments. This would definitely help me out 😉 !  What are microservices? Let’s start with defining the microservice term. In a common approach, we design our system as one huge „being”. Of course, there mig...

Dziel się z innymi:
gifty - Architecture overview - Forever F[r]ame

Daj się poznać 2017 1173 dni, 7 godzin, 19 minut temu dpawlukiewicz 48 źrodło rozwiń

I often work on applications whose sole task is to execute a script at certain time or day. You may approach it in several ways, eg.: Task Scheduler (Windows), SQL Job (if it is a SQL task) or CRON in Linux. You may also write application, which would run in background and execute a script at certain time. The only question is – do you really want do it? In this post, I would like to introduce other solution to tasks like this. ...

Scheduled jobs made easy - Topshelf and Quartz.NET |

Programowanie rozproszone 1225 dni, 5 godzin, 55 minut temu Mateusz Pustelak 282 źrodło rozwiń

Not so long ago, I’ve eventually decided to dive into the world of microservices. I did look for an opportunity to make use of this architectural pattern for quite some time and finally was able to do so. After 3 months of trying out the new things and learning stuff mostly on my own (the hard way) I believe it’s a good time to share some of my experience. I have no doubts that at some point in the future when I look back at this post I might be like – “oh God, what was I thinking back then, it’s so wro...

Dziel się z innymi:
So I’ve been doing microservices | Piotr Gankiewicz

Programowanie rozproszone 1275 dni, 8 godzin, 1 minutę temu spetz 202 źrodło rozwiń

It’s been quite a while since I’ve started gathering some knowledge about the microservices architectural pattern that’s been on a hype recently. After reading many articles, some books like Microservices in .NET Core and talking with smart guys in the Devs PL Slack channel, I’ve eventually decided that the time has to come to try to make the microservices happen in the real world project. That’s the beginning of my journey into the distributed programming and architecture, so please keep that in mind wh...

Dziel się z innymi:
[EN]Microservices, here I come | Piotr Gankiewicz

Architektura 1337 dni, 8 godzin, 17 minut temu spetz 245 źrodło rozwiń

I suppose there are not so many people who do not know what Node.js is. You may love it, you may hate it, but you cannot deny the fact that more and more enterprises are using it to replace some parts of their system, previously written in Java, Rails or .Net.  Node.js runs in a lot of environments – starting from large, multi-core servers, through laptops, then microcomputers like Rasperry Pi, finishing on IoT devices...

Dziel się z innymi:
[EN] Developing Node.js App Services in TypeScript – part 1 of n: Introduction. – Epikia

Web 1409 dni, 17 godzin, 41 minut temu piotrgasiorowski 82 źrodło rozwiń

Jak wybrac losowy port do hostowania np. mikro serwisu? Jaki zakres portow wybrac? Jak sprawdzic, czy port jest wolny?

Dziel się z innymi:
Find free port for your application - Michal Dymel DevBlog

Daj się poznać 2016 1492 dni, 6 godzin, 45 minut temu Michal Dymel 72 źrodło rozwiń

Zmiana koncepcji na rozwiązanie problemu services registry w MiSeCo

Dziel się z innymi:
MiSeCo #9: Services Registry – Michał Dymel – DevBlog

Daj się poznać 2016 1499 dni, 8 godzin, 3 minuty temu Michal Dymel 29 źrodło rozwiń

MiSeCo #8: Service discovery methods ?>michalComments 0 Comment This is an 8th post in a series about MiSeCo – a project I am working on for the “Daj się poznać” challenge (in Polish). So far I have implemented a way of calling service methods remotely over HTTP protocol. Currently, service URL is hard-coded in the application. I need to find a way to allow services register automatically so that very little configuration is needed. Initially, I wanted to create MiSeCo in the way that there is no c...

Dziel się z innymi:
[EN] Service discovery methods in microservices architecture – Michał Dymel – DevBlog

Daj się poznać 2016 1504 dni, 4 godziny, 32 minuty temu Michal Dymel 53 źrodło rozwiń

Kontynuacja zdalnego wywoływania metod w microservices.

Dziel się z innymi:
MiSeCo #7: Communication – Michał Dymel – DevBlog

Daj się poznać 2016 1507 dni, 6 godzin, 56 minut temu Michal Dymel 40 źrodło rozwiń

Kolejny wpis o MiSeCo. Tym razem opisuje strukturę projektu oraz wstępne założenia implementacji.

Dziel się z innymi:
MiSeCo – project structure – Michał Dymel – DevBlog

Daj się poznać 2016 1538 dni, 3 godziny, 42 minuty temu Michal Dymel 60 źrodło rozwiń

Wstęp do MiSeCo: MicroServices framework based on ASP.NET Core. Mój projekt na #dajsiepoznac

Dziel się z innymi:
[EN] Introduction to MiSeCo – Michał Dymel – DevBlog

Daj się poznać 2016 1541 dni, 8 godzin, 52 minuty temu Michal Dymel 48 źrodło rozwiń

This post describes how to minimize overhead when developing systems with microservices architecture, especially as it comes to development and deployment. Some time ago, we published similar post about solving this problem in Microsoft and Azure world. This time we will focus on AWS, Java, Spring Boot, Docker and some useful open source libraries from Netflix.

[EN] Microservices with minimum overhead using Spring Cloud, Docker and AWS ECS | Future Processing

Inne 1595 dni, 14 godzin, 16 minut temu FutureProcessing 97 źrodło rozwiń

This is the second one of two posts concerning approach to build cost effective, but prepared for scaling, systems using ASP.NET Web API and Azure.

[En]Microservices with minimum overhead using ASP.NET Web API and Azure – part 2 – Deployment | Future Processing

Architektura 1713 dni, 20 godzin, 25 minut temu FutureProcessing 166 źrodło rozwiń

This is the first one of two posts concerning approach to build cost effective, but prepared for scaling systems, using ASP.NET Web API and Azure. In the era of building systems that aim to provide services at global scale, requirements for scalability and high availability are becoming our bread and butter. What is more, it is absolutely normal that stakeholders want first shippable version of software as soon as possible.

Microservices with minimum overhead using ASP.NET Web API and Azure – part 1 – Architecture | Future Processing

Architektura 1728 dni, 7 godzin, 35 minut temu FutureProcessing 163 źrodło rozwiń

Tyle się mówi o rozwoju programistów. Ba, sam o tym często gadam. Że to dobre, że trzeba, żeby nie stać w miejscu a iść do przodu… Ale powiedzcie mi: jak ma się rozwijać programista w typowym programistycznym polskim (i pewnie nie tylko) dev-kołhozie? Przychodzi do roboty, siada do projektu, po 8h wstaje i wychodzi. Niby normalka, ale… niekoniecznie. Moim zdaniem kluczowe jest pytanie: do jakiego projektu ten pr...

Architektura przyjazna rozwojowi programisty | Maciej Aniserowicz o programowaniu

Inne 2072 dni, 7 godzin, 45 minut temu psz750 452 źrodło rozwiń

1 2


(32 895,6)
(32 816,53)
(27 178,29)
(21 178,88)
(20 336,33)
(13 018,14)
(10 512,43)
(9 775,28)
(8 388,28)
(6 822,96)
(6 214,22)
(5 393,84)
(4 127,41)
(4 026,73)
(3 908,07)
(3 599,64)
(3 448,35)
(3 318,39)
(3 224,66)
(3 173,43)