Business people don’t want to pay for integration anymore. Integration can eat up to 50% of a project’s budget because you must pay for developing reliable infrastructure, programming of API’s adapters, as well as spend time and money on the teams coordination. After the project is released, you’ll find that APIs suddenly change on all integration points. It means you’ll have to invest money in integration tasks infinitely.
One of my clients, whom I developed new microservices architecture for, asked us to develop integration through iPaaS instead of buying an outsourcing company as he did before. …
We almost always want to split an awkward monolith enterprise application into small pieces because business desires to reduce time to market, do fast experiments and deliver features continuously when they are ready with no delays. It is easy to achieve these requirements with architecture that consists of a bunch of self-described business-functions coupled with really small functional pieces, i.e. Microservices.
The key idea in microservice architecture is to create small (really small) services, develop and deploy them independently. Each microservice uses its own database and could be written in any programming language.
We’ve spent the last 4 years working with big enterprise companies as an external IT development team and IT-consultants. Most of our clients are from e-commerce or retail businesses, but I’m sure the following problems and solutions fit for other industries.
Big companies such as giant e-commerce and financial companies often have their own IT, design and marketing departments. It looks like they have all the necessary things and resources to develop the best ever software for market conquest.
Indeed, they have problems in implementing internal IT innovations or bringing new IT-products to the market. …
The issues can be found and fixed during Stand-up Meetings, so called briefings, Daily Scrums, which are strongly recommended by gurus of Scrum and eXtream Programming.
This is a cheap and very effective practice you can implement in your company. A meeting is held by the whole product team daily. Each member answers three simple questions:
Conducting standups for more than eight years on different teams, companies and in different countries…
We use microservices a lot at Byndyusoft. But we feel there are not enough competitive books and articles on this subject. Therefore, two big conferences is a good chance to get the newest information about a Microservice architecture and everything that surrounds it.
Check out how many impressive public reports are prepared for microservice fans in these conferences!
My recommendations for attending the OSCON public reports:
In my consultant practice, I have made a lot of attempts to change processes and engineering culture in my client’s companies. Not all attempts were successful. I found that some organizations first started the Agile transformation on a motivated impulse but after a few months was eaten by the Waterfall culture again.
For example, I gave Scrum training to client’s employees. Then together with a client’s team we released 3–4 Sprints. After successful releases, I left developers and the Product Owner to themselves. …