My phone's running out of juice so I'll have to cut this short. I'll make a note of anything else of interest.
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
An alternative to big switch handler for messages.
7 years ago
Using command pattern with action and role in the json.
7 years ago
Gangnam style is playing I'm the background :-D
7 years ago
We want to support maps, arrays, strings, numbers, maybe binary data? Maybe streams?
7 years ago
We don't want an API just to remote distribute the model. There is something wrong with this journrujourney, something isn't working.
7 years ago
7 years ago
Well, are they? I can't help but feel he's driving at something.
7 years ago
Do we need inheritance? Can be good, but we can't serialise classes and distribute them.
7 years ago
Do we really need accessors?
7 years ago
Encapsulation is good.
7 years ago
What is an object?
7 years ago
I've seen @matteocollina speak before, so I'm looking forward to this. #muCon2015
7 years ago
Links.
7 years ago
:-D
7 years ago
Some useful things to check out for preparing for failure and recovery. Particularly interested in symptom based monitoring.
7 years ago
Apparently healthcare.gov used CNN as their monitoring! #muCon2015
7 years ago
Hell yeah!
7 years ago
Architecture is about risk management.
7 years ago
This is probably the best way to move to microservices, they is, not necessarily moving to them. Allow your team the opportunity to evolve to microservices by giving them autonomy and room to experiment.
7 years ago
Ha! #muCon2015
7 years ago
7 years ago
Focus on products, not projects.
7 years ago
Lol about manifesto
7 years ago
Microservices from a business and people point if view.
7 years ago
You can check it out here.
7 years ago
7 years ago
Difficult to commentate a code demo, but probably worth following these guys/poles on twitter etc.
7 years ago
I'm no Java developer, but Java 8 looks quite bearable :-)
7 years ago
We're going to code BAAS (beer as a service) #muCon2015
7 years ago
7 years ago
Promising title for the next talk.
7 years ago
I think Guarav just invented the word "updation". #muCon2015
7 years ago
True. Good architecture can exist in a monolith, just like we have seen bad architecture (many times over) in a microservices approach.
7 years ago
The manifesto they developed. Pretty similar to how we work at the Mail Online. Particularly keeping management tools and ceremonies to the bare minimum. I agree that stand-ups are a distraction.
7 years ago
The problem with rockstar syndrome.
7 years ago
What happens when your rockstar quits.
7 years ago
This was for a big project for a company called Bridj, an Uber like bus service in Boston.
7 years ago
Consulting does not sound as good anymore.
7 years ago
Next talk by Guarav Gaglani
7 years ago
Advocates PRY rather than DRY for internal libraries to reduce dependencies between services. He says it makes it easier to burn code to the ground to rewrite without dependencies.
7 years ago
Don't enforce standards, offer good tools and solutions that are easy to implement. Evangelise solutions rather than force them on your team.
7 years ago
Don't be afraid to sacrifice, and justify this sacrifice to management. It's more wasteful to keep a lane piece of software hanging around.
7 years ago
Aim for the quality you need. The highest quality is expensive and often wasteful. The first iPhone is a good example.
7 years ago
7 years ago
Operating your own infrastructure is very costly.
7 years ago
It isn't, the responsibility needs to be shared with developers. Embrace extended devops for all teams.
7 years ago
What have they learnt.
7 years ago
And now what they have.
7 years ago
Nice photo of a monolith.
7 years ago
New talk with Erik Lindblad. This talk is about scaling from 12 engineers with a monolith to more than 300 with a microservices based architecture.
7 years ago
We must remember that microservices are potatoes, not apples. #muCon2015 @netkernel
7 years ago
Yet another speaker to equate microservices with Unix philosophy.
7 years ago
And with enough of these spaces, you can build anything. All if these nodes are completely uncoupled. He's got about 1000 services, and 4000 endpoints in his system.
7 years ago
We only have to think about 3 things, spaces, requests and endpoints.
7 years ago
You can't have a centralised registry for a technology that runs on the Web. The responsibility for the state sits with the endpoint.
7 years ago
I'll let the slide speak for itself, but basically HTTP may not be the best protocol for microservices.
7 years ago
Microservices are not the actor pattern. They are something new and different. #muCon2015
7 years ago
A composite is greater than the sum of its parts.
7 years ago
Peter holding an "earth apple". Lovely metaphor about different cultures attaching existing perceptions to new ideas. Many people view microservices through the lense of what they already know.
7 years ago
Next talk by Peter Rogers.
7 years ago
Lol, there's a link for ball gags. #muCon2015
7 years ago
Remember, there is a level of pain you have to go through, before the pleasure kicks in.
7 years ago
7 years ago
People rarely read about microservice patterns before starting out.
7 years ago
Documentation should be a solved problem, but we seem to reinvent the wheel every decade. Swagger seems to be the best of a bad bunch.
7 years ago
Ugh, this doesn't deserve an explanation.
7 years ago
How do you find a service?
7 years ago
The drivers for moving to a microservices architecture. Social and technical.
7 years ago
Standard microservices problems.
7 years ago
It's difficult, it's painful, so why are we doing this.
7 years ago
7 years ago
This talk looks interesting! #muCon2015
7 years ago
Full disclosure, I tuned out for this one.
7 years ago
*nods head* (I have no idea what's going on)
7 years ago
Hmm... Indeed.
7 years ago
This guy is forced to rush as he planned a 1 hour talk and he now has less than 30 minutes. Consequently I have no idea what's going on.
7 years ago
It's the 23 Ps... I mean 6.
7 years ago
New talk.
7 years ago
Demo! Ok that was pretty cool. Node goes down, node comes back with its state.
7 years ago
7 years ago
He's just been told he's running late. This guy can talk.
7 years ago
Docker plugins.
7 years ago
Diagram of how Flocker works. Notice the more politically correct version of master/slave.
7 years ago
Flocker treats a container and data volume as a single atomic unit. We're almost at the demo :-)
7 years ago
And this is the part where you specify your resources.
7 years ago
A Marathon manifest.
7 years ago
Plus you can write your own frameworks.
7 years ago
7 years ago
Mesos will manage resources while a framework does stuff with those resources. Mesos isn't about containers, you can run anything with it.
7 years ago
Stateless things are easy to containerise, but stateful services get left out. Now Kai is going to demo how you can do it.
7 years ago
These tools handle many jobs across many machines.
7 years ago
Kai has promised to demo us an automatic recovery of an microservice with state intact.
7 years ago
Scheduling is like a giant game of tetris, but hopefully when you get a row, the servers don't all disappear.
7 years ago
Forget about your hardware, use an orchestrator.
7 years ago
Containers are great at handling processes, but what do we do about the data. If a node has its own data and goes down, what happens to that data.
7 years ago
Each service will be unique and want it's own database that fits the purpose. This is going to require more processes.
7 years ago
Trying to solve the state problem in docker containers, or any cluster.