> The number of developers today who assume their user base will grow, and optimise for that, when it's not required, far exceeds the number who assume their user base won't grow, and have growing pains because of it.
I think discussing this point is useless. For the same of the argument assume we are.
> Also, this is exactly what horizontal scaling is for, which you need to deal with regardless of whether you're using micro services or not.
I give you that. You can. I don't think it's a correct approach, but you can def just scale once you hit your smallest bottlenecks and you'll be fine (I think).
>first off - you're still comparing yourself to a massively different field. If you are working for a bank, you shouldn't be asking for this type of advice, unless you've lied to them about your skills.
>secondly - those things you described are all different applications within a bank. There may be some integration but more likely the common point for them all is a massive mainframe system that they all interact with. That is not micro services.
I'm confused. How do you know which field I'm working in? I am comparing us to a bank because like I said, the services we offer are very similar. I shouldn't be asking for advice? That's plain ignorant. I am asking for the advice because I am a strong believer in micro services but I figured I'd rather ask people for their opinion to see what I get without the title giving away my thoughts. I doubt you would have clicked this thread if what you read was an opinionated title saying "Micro services are the only way" at least I wouldn't. I'd assume that persons mind won't change. Instead I wanted to get as much feedback as possible (including yours :) ).
While the banking world moves slow, and tends to make up new terms for anything they do to make them sound cooler. The newer core banking systems (check out cloud banking, micro service banking) are usually composed of smaller services that communicate through some buss and managed through one uniform API. I'm pretty sure that's along the lines of micro services or at the very least more micro than mono! -- When I say new I mean within the last 10-15 years. I worked at Citigroup and they had that structure implemented on so many of their products.
I don't think I'm convinced. But maybe I'm missing something ?
You can't go on assuming user base won't grow. Also massive is not a quantifiable amount. There are certain thresholds that require the application to scale, and those depend on the functionality expected. If I hash passwords, but I can only hash 100 at once. If I offer integration API's that get hit more often than my actual site. Will I need to scale my monolith app for those specific cases?
To say that a large application let's you focus on just dev work is a bald statement in my opinion. A large application is harder to test, harder to deploy, changes have a higher risk, risk of data leaking by mistake, very coupled, and not simple -> harder to design for -> harder to move stack. Just on boarding an engineer into a monolith app from my experience is hard..
I'm not sure how with micro services you're worried about the processes? I lost you there..
I have a quick script that spits out a microservice with basic health endpoint. I made a communication module that uses sockets and parent as a bus to communicate through.
A bank offers some sort of signin application, statement generating (sent to email), some api's for payroll, and maybe an integration with a credit card where it notifies customers about any purchases made. When sign in is down, it doesn't mean you shouldn't get alerts about CC purchases, or that reports shouldn't be generated. Even when you're signed it's possible certain feature might not be active. With a mono if a bug took down the application every service you offer is down. --- This scenario is very much around the kind of service we want to provide.
My initial response to the team when I heard the proposal was that programming is an art form. There is a beauty how software is organized and orchestrated.
Given that the microservices do very different things, combining them together will do nothing but clutter a the code base. JS gives an excellent module system which allows for maximum code reuse. That should be emphasized. But combining 6 code bases together into a project that is planning to expand extensively over the next year makes little to no sense at least to me.
Depends on how advanced you want your routing to be I can see going with the from scratch rout, but that means you'll need to spend time writing unit tests..
You might as well fork and delete/modify a bunch of code.
I just moved back here from NYC. I was working in automated trading. You want to apply to 2sigma and bridgewater. They value smarts over experience. You can also work for Chase, Citi Group, Citi Bank, CapitalOne.
If you wanna become a quant, or do anything related to actual decision making of when a purchase order is processed or when it's dropped. You'll need at least a masters in Mathematics or Engineering, and be fluent in C/C++ for finance.
I will tell you right away. As a developer even if you knew your stuff you'll always be a developer. When shit hits the fan you'll be the first out the door.
Lastly, you need to learn the language. You'll need to know all these terms that many will refuse to explain to you because that's what earns them value. Our director of engineering used to always say the only reason he still has the job is because he understand the language.
-- I worked at Citi Group.
Overall I hated nyc. I lived my whole life in California. Didn't have to wear dress cloths to work, didn't have to be at work at 7:30-8 am sharp, but the money was great.
I started my professional experience at 18 I have indeed been through the struggle of proving myself to older members of the team who at first disapproved. Although now I feel like I know how to handle these situations.